Always false float comparisons

[Manu via Digitalmars-d]

On 9 May 2016 at 19:10, Walter Bright via Digitalmars-d
<digitalmars-d at puremagic.com> wrote:
> Don Clugston pointed out in his DConf 2016 talk that:
>
>     float f = 1.30;
>     assert(f == 1.30);
>
> will always be false since 1.30 is not representable as a float. However,
>
>     float f = 1.30;
>     assert(f == cast(float)1.30);
>
> will be true.
>
> So, should the compiler emit a warning for the former case?

Perhaps float comparison should *always* be done at the lower
precision? There's no meaningful way to perform a float/double
comparison where the float is promoted, whereas demoting the double
for the comparison will almost certainly yield the expected result.