To be fair, I'm not sure I like the make-commas-optional approach either. But, the solution occurred to me as possible, so I thought it was worth considering as we're exploring the design space.
And, yes, I was suggesting only to make them optional, not to require everyone remove them. Richard On Sep 26, 2014, at 5:34 PM, Brandon Allbery <allber...@gmail.com> wrote: > On Fri, Sep 26, 2014 at 5:21 PM, Johan Tibell <johan.tib...@gmail.com> wrote: > I don't think that's necessarily is good style. I don't think we want two > different ways of doing import lists. > > Yes; I kinda hate the idea myself, it encourages an unreadable programming > style. But it's not the wholesale breaking change you were suggesting, either. > > -- > brandon s allbery kf8nh sine nomine associates > allber...@gmail.com ballb...@sinenomine.net > unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net > _______________________________________________ > Glasgow-haskell-users mailing list > Glasgow-haskell-users@haskell.org > http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
