Always false float comparisons

[Walter Bright via Digitalmars-d]

On 5/9/2016 12:39 PM, tsbockman wrote:
> Educating programmers who've never studied how to write correct FP code is too
> complex of a task to implement via compiler warnings. The warnings should be
> limited to cases that are either obviously wrong, or where the warning is likely
> to be a net positive even for FP experts.

I've seen a lot of proposals which try to hide the reality of how FP works. The 
cure is worse than the disease. The same goes for hiding signed/unsigned, and 
the autodecode mistake of pretending that code units aren't there.