|
|
|
|
|
by Peaker
5463 days ago
|
|
Perhaps Haskell compromised on first-class modules. But ML compromised on: * Type-classes (which overlap but aren't really the same thing and are probably more important) * Typed-effects (a.k.a purity): This is a big one to lose. * Laziness/Strictness control I think ML is more of a compromise than Haskell. |
|
http://www.cs.nott.ac.uk/%7Egmh/appsem-slides/peytonjones.pp...
I personally disagree. I'm pretty sure laziness has made it much easier for me to try out an idea. If it works, then I'll test that I didn't space leak. The notion of it almost makes me feel dirty. ;-) :-P