Always false float comparisons

[Joseph Rushton Wakeling via Digitalmars-d]

On Thursday, 19 May 2016 at 11:33:38 UTC, Joakim wrote:
> The example he refers to is laughable because it also checks 
> for equality.

With good reason, because it's intended to illustrate the point 
that two calculations that _look_ identical in code, that 
intuitively should produce identical results, actually don't, 
because of under-the-hood precision differences.