Re: Permitting trailing commas for record syntax ADT declarations

I don't think that's necessarily is good style. I don't think we want two different ways of doing import lists. The original proposal was to address a quite small but important engineer issue: without allow *one* trailing comma your version control history gets messed up, because the wrong person gets "blamed" for a line of code. The standard programming language way of solving that problem is to allow a trailing comma. On Fri, Sep 26, 2014 at 11:16 PM, Brandon Allbery wrote:

On Fri, Sep 26, 2014 at 5:12 PM, Johan Tibell wrote:

...

That would be nice if we had a clean slate, but I don't people are going to change their whole import lists now.

I read the proposal as making all commas optional, not as requiring them to not be present.

-- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net