Ord methods are surprisingly strict

[Sven Panne]

Am Do., 7. Mai 2020 um 20:53 Uhr schrieb Christopher Allen <
cma at bitemyapp.com>:

> If one of my applications develops a memory leak because of this potential
> change, where should I invoice you for the time wasted tracking down &
> fixing it? My short-term contract rate is $250/hour but I could be argued
> down to $200/hour.
>

Sorry if I was unclear: I didn't propose to change the strictness of the
Ord instances for the Prelude types, quite the opposite: As I said (with
reference to the report), they are basically carved in stone. If someone
wants lazier instances, they would e.g. have to use a newtype wrapper + new
Ord instances. And they should better document the unusual strictness
clearly...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/libraries/attachments/20200507/d714c2fa/attachment.html>