Iavor S. Diatchki
Iavor S. Diatchki
I think it should be disallowed, as it is a common source of errors, at least for me. Also, I can't think of any particularly compelling use cases of allowing...
Of course---I added this proposal because someone suggested at it during the State of Haskell discussion at the Haskell Symposium. Please do add additional pros and cons if you know...
This sounds like something the libraries committee should decide on.
People have suggested that a much more natural notation for LambdaCase is: ``` case of { P1 -> e1; P2 -> e2 } ``` Thus LambdaCase may be explained simply...
I am in support of this proposal too---I think it fits very naturally with other sections.
I am with @nhn1966 on this one---I do quite a bit of Haskell development on a daily basis and I never use `\case` or find the need for it.
I was thinking that grammar changes are fairly straight-forward, namely simply allow for the expressions in a tuple to be optional. ``` aexp → ([exp1] , … , [expk]) (k...