News for hackers. Stuff that matters.

A comment on Haskell Problems for a New Decade. Parent comment

Re:Haskell Problems for a New Decade by tome on Saturday January 25, 2020 @03:23AM (#22145374)
Haskell language extensions do not change the language semantics. They extend the semantics with additional functionality. Existing code does not change its meaning when you enable an extension.
[ Parent | on HN ]
Re:Haskell Problems for a New Decade by patrec on Saturday January 25, 2020 @06:11AM (#22145813)
Strict. Not a change in language semantics at all.
[ Parent | on HN ]
Re:Haskell Problems for a New Decade by tome on Sunday January 26, 2020 @06:16AM (#22151557)
Ah, great counterexample! StrictData is another. Do you know any others that change language semantics non-trivially? I would roughly define "non-trivially" to mean "correct programs become incorrect".

By the way, I'm particularly interested because I am writing about Haskell myths. I have a very rough draft at http://h2.jaguarpaw.co.uk/posts/haskell-myths/

[ Parent | on HN ]
Re:Haskell Problems for a New Decade by cannabis_sam on Sunday January 26, 2020 @01:40PM (#22153780)
There’s also QuasiQuoter which can make valid code with list comprehensions not compile, but it doesn’t just compile it, it gets stuck looking for the end tag. Not sure if that qualifies :P
[ Parent | on HN ]