News for hackers. Stuff that matters.
Re:Reflecting on Haskell in 2017 by yorwba on Monday December 04, 2017 @01:40AM (#15841948)
But are all those options compatible with each other?
Re:Reflecting on Haskell in 2017 by jeremyjh on Monday December 04, 2017 @06:58AM (#15843241)
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

Re:Reflecting on Haskell in 2017 by tome on Monday December 04, 2017 @05:22AM (#15842867)
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.)
Re:Reflecting on Haskell in 2017 by shmish111 on Monday December 04, 2017 @11:05AM (#15844858)
GeneralizedNewtypeDeriving and DeriveAnyClass (although this is fixed in 8.2)