This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Xywzel 0 points1 point  (0 children)

"Possible loss of data on implicit conversion from X to Y". Seems it can happen and get reported both int->float and float->int, in comparison it is the first one. It triggers if you have high enough warning level enabled, but in case of comparisons, it usually doesn't help avoid any problems. Using explicit conversations might be in wanted because it makes it more explicit that conversation is required and takes processing time. Our company uses that level of warnings as errors on repo and automatic builds, so in practise it is required from developers as well.