Can we please make a law against == operators that do stupid things with mismatched types?
When the cost matters you can always use matching types, either for the underlying operands in the expressions or both sides or by casting one or both sides.
-
-
(1<<28)+1==0x1p28f is misleading. (float)((1<<28)+1)==0x1p28f is obviously reasonable.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
if you get an error, you can be aware in order to do that. if it silently switches to more expensive behavior, that's harder
-
You could always enable such a warning if you want to. I don't think the "more expensive behavior" is significantly more expensive in most cases, and the vast majority of comparisons are not performance bottlenecks anyway.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.