2009/08/27 Bulat Ziganshin :

...stop reusing Prelude operators, in particular, replace "-" with "$"?

I have to say, the `$ do` construct is an eyesore and `- do` is a lot easier on the eyes. Would it introduce ambiguity in the Haskell grammar if foo do... foo case... foo if... were always parsed as: foo (do...) foo (case...) foo (if...) This is what is usually meant. -- Jason Dusek

On Aug 30, 2009, at 14:56 , S.Doaitse Swierstra wrote:

On 28 aug 2009, at 08:11, Jason Dusek wrote: 2009/08/27 Bulat Ziganshin :

...

...

...stop reusing Prelude operators, in particular, replace "-" with "$"?

I have to say, the `$ do` construct is an eyesore and `- do` is a lot easier on the eyes.

Would it introduce ambiguity in the Haskell grammar if

foo do...

foo case...

foo if...

were always parsed as:

foo (do...)

foo (case...)

foo (if...)

For the first two it would not make a difference, since they are essentially closed constructs, following the offside rule which inserts a } at the place where they end, so this cannot give rise to an ambiguous interpretetation. One might even argue that their current precedence level in the Haskell definition is "suboptimal". The "if" is a different thing, due to the absence of offside rules for if.

mapM. And yes, I know about forM; are there any other examples of this? -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery@kf8nh.com system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH

Jason Dusek wrote:

Say we have a nice thread on this and we all realize that the precedence of `do` and `case` could be changed (and changing `if` would be nice but we can't have everything). How many months/years would it take for any change in that direction to occur?

Seven! (Sorry, working on theses on Sunday evenings makes for silly moods.)