4 ms·
Honestly this bugs me too. I don’t really see why the community doesn’t just decide the GHC really IS Haskell. I’m aware there are other compilers but basicall
by MBCook 9y ago
Honestly this bugs me too. I don’t really see why the community doesn’t just decide the GHC really IS Haskell.
I’m aware there are other compilers but basically everyone uses GHC. So all these things that have to be turned on because they’re not “compatible“ with all the other compilers that no one else uses just add complexity for new users (and I suppose current users.)
- yorwba 9y agoBut are all those options compatible with each other?
- forkerenok 9y agoNo, they are not, and some are useless Edit: I guess not useless, but over time rendered as anti-features
- tome 9y agoCan you name some extensions that are not compatible with each other. I can't, off the top of my head, and I've been using Haskell for some years. (I don't deny there might be some, but I'm finding it hard to think of any.)
- shmish111 9y agoGeneralizedNewtypeDeriving and DeriveAnyClass (although this is fixed in 8.2)
- jeremyjh 9y agoYes they are but they may not be compatible with all existing code as it is presently written. For example turning on OverloadedStrings can introduce type ambiguity in existing code where the type of a string literal cannot be deduced.
- jcelerier 9y agoyeah and we should also have decreted that IE6 was Internet in 2003 because that's what everyone was using too
- marcosdumay 9y agoGHC or not, you simple do not want all the extensions active all the time.