Re: Proposal (long term): Remove (/=) from Eq; change the semantics of (==) for floating point

point being, Floating point is weird, but it *does* obey an approximate (bounded relative error) version of the standard algebraic laws, but most folks are unaccustomed to that (admittedly WEIRD/Different) style of thinking On Thu, Sep 25, 2014 at 1:19 AM, Carter Schonwald < carter.schonwald@gmail.com> wrote:

i'm strongly -1 on doing ANYTHING resembling instance Eq Double where x == y = decodeFloat x == decodeFloat y

floating point is odd because it kinda has to be, and changes to the defaults for that need a lot of discussion about the implications (even before they got to the libraries list).

On Thu, Sep 25, 2014 at 1:05 AM, Johan Tibell wrote:

...

-1

This would make floating point values a pain to work with for seemingly little gain.

_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries