Always false float comparisons

[ixid via Digitalmars-d]

On Wednesday, 18 May 2016 at 11:38:23 UTC, Manu wrote:
> That's precisely the suggestion; that compile time execution of 
> a
> given type mirror the runtime, that is, matching precisions in 
> this
> case.
> ...within reason; as Walter has pointed out consistently, it's 
> very
> difficult to be PERFECT for all the reasons he's been 
> repeating, but
> there's still a massive difference between the runtime 
> executing a
> bunch of float code, and the compile time executing it all 
> promoted to
> 80bits. Results will drift apart very quickly.

What do you think can be productively done to improve the 
situation? I am beginning to think a Wiki-like structure would be 
better for these discussions where each major debater has their 
thoughts on a specific issue in a relevantly headed section so 
there is more clarity.