Re:Reflecting on Haskell in 2017
by marcosdumay on Monday December 04, 2017 @11:51AM
(#15845266)
GHC or not, you simple do not want all the extensions active all the time.
But are all those options compatible with each other?
Yes 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.
Re:Reflecting on Haskell in 2017
by forkerenok on Monday December 04, 2017 @02:35AM
(#15842203)
No, they are not, and some are useless
Edit: I guess not useless, but over time rendered as anti-features
Can 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.)
GeneralizedNewtypeDeriving and DeriveAnyClass (although this is fixed in 8.2)
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.)