Re: [ghc-steering-committee] [ghc-proposals/ghc-proposals] RecordDotSyntax language extension proposal (#282)

It's a very well written proposal, indeed. I've already paged out the details of the syntax we agreed upon. But I'm not sure that the parenthesis-based example in Section 5 (Costs and Drawbacks) is correct in the current specification. Simon, you should probably check this. That's pretty minor at the end, just a consistency thing. It's all good for me. On Sat, Apr 18, 2020 at 12:16 AM Simon Peyton Jones via ghc-steering-committee wrote:

Dear GHC steering committee

Shayne and Neil have updated the RecordDotSyntax proposal in the light of our conclusions.

We have debated this extensively, so the question is now not so much about content as presentation: is the proposal complete, clear, and precise?

I think it’s pretty good, and I propose that we now accept it as-is. I’ll take silence as assent. Please yell by close of play Weds 22 April if you’d like any further changes.

Thanks!

Simon

*From:* Shayne Fletcher *Sent:* 11 April 2020 17:59 *To:* ghc-proposals/ghc-proposals *Cc:* Simon Peyton Jones ; Mention < mention@noreply.github.com> *Subject:* Re: [ghc-proposals/ghc-proposals] RecordDotSyntax language extension proposal (#282)

@simonpj https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsimonpj&data=02%7C01%7Csimonpj%40microsoft.com%7Caece2c82e6944e94fd2c08d7de399932%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637222211273896163&sdata=2OEMDHtyImmbTySwUAOI1RpY35MMTCstKj97qCn3Aa0%3D&reserved=0

I'd like to invite the authors to update their proposal to incorporate (C2a)

We are happy to report that the proposal has been updated as per the committee's requests.

- To write out the changes to the grammar, especially how to deal with specifying aexp2.x (see Note 5)

See section 2.3 https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fshayne-fletcher-da%2Fghc-proposals%2Fblob%2Frecord-dot-syntax%2Fproposals%2F0000-record-dot-syntax.md%2323-lexing-and-parsing&data=02%7C01%7Csimonpj%40microsoft.com%7Caece2c82e6944e94fd2c08d7de399932%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637222211273906160&sdata=OI78P06S7Wj1VyXsBzZTGvdoZQh28WNSshAa1fUyms8%3D&reserved=0 .

- To address the question of what happens if a field name is an operator (see Note 6)

See section 2.1.3 https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fshayne-fletcher-da%2Fghc-proposals%2Fblob%2Frecord-dot-syntax%2Fproposals%2F0000-record-dot-syntax.md%23213-fields-whose-names-are-operator-symbols&data=02%7C01%7Csimonpj%40microsoft.com%7Caece2c82e6944e94fd2c08d7de399932%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637222211273906160&sdata=hoJv8DppPZEo5WHQ2uvnYSofC5X03PF2wnkHBCqgWYo%3D&reserved=0 .

Then the committee can do a final review and sign it off.

We should now like to formally request the committee's final review and sign off. We thank once again yourself and the committee for your time and consideration!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fghc-proposals%2Fghc-proposals%2Fpull%2F282%23issuecomment-612465003&data=02%7C01%7Csimonpj%40microsoft.com%7Caece2c82e6944e94fd2c08d7de399932%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637222211273916152&sdata=IMIqX%2BuXd1z6VqUNg4PSYk2IlmonYwsaK18a3Ds3KyU%3D&reserved=0, or unsubscribe https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAEOY67QJRH5V7O2RQGDB3LRMCOULANCNFSM4I7VWDFQ&data=02%7C01%7Csimonpj%40microsoft.com%7Caece2c82e6944e94fd2c08d7de399932%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637222211273916152&sdata=MAq7dcOiPu56n3hb7ElQcgftlxaDhV84A8mj9Pu4U3Y%3D&reserved=0 . _______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee