Re: Remove Enum from Float and Double

[harry]

Johan Tibell johan.tibell@... writes:

 If we truly believe that the instance is dangerous for users (and not
merely for people who don't understand floating point arithmetic on
computers), then we should add a deprecation pragma to the instance and
discourage its use. But what would the deprecation message encourage
instead, for users to write an explicit loop that tests against some
lower/upper bound? It would have the same problem as enumFromTo. I think the
issue here is really that floating point math on computers is hard to think
about.

The issue is that these instances encourage problematic code. People who
know what they're doing can write whatever they want, but we shouldn't be
handing out unstable explosives on street corners :-)


___
Haskell-prime mailing list
Haskell-prime@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-prime

Re: Remove Enum from Float and Double

[harry]

Tillmann Rendel rendel@... writes:

 In general, I would be against removing features just because they are 
 confusing for beginners. I don't think that's a good design principle 
 for a language that is primarily targeted at professional programmers 
 and computer scientists.

They're confusing to beginners because they don't have consistent or
sensible semantics. That should bother the professional programmers and
computer scientists too!


___
Haskell-prime mailing list
Haskell-prime@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-prime