RE: Implementing pattern synonym constructor signatures

2018-01-15 Thread David Feuer
3. Someone could write pattern P x <- ... where  P :: ...  P x = ... The pattern signature has to be the same as the constructor signature except for constraints, so it doesn't necessarily sound trivial to infer. David FeuerWell-Typed, LLP Original message From: Simon Peyton

Re: Implementing pattern synonym constructor signatures

2018-01-15 Thread David Feuer
Never mind about parsing. It looks like the parser is already doing what it needs to do and I need to look to RdrHsSyn.hs. David FeuerWell-Typed, LLP Original message From: David Feuer Date: 1/15/18 2:10 PM (GMT-05:00) To: Simon Peyton Jones

RE: Implementing pattern synonym constructor signatures

2018-01-15 Thread Simon Peyton Jones via ghc-devs
0. Parsing. I wasn't actually able to find the code that parses pattern synonyms. Can someone point me in the right direction? Parser.y line 1356, production ‘patteron_synonym_decl’ looks plausible. Currently we have data HsPatSynDir id = Unidirectional | ImplicitBidirectional |

Re: Implementing pattern synonym constructor signatures

2018-01-15 Thread David Feuer
See the accepted proposal:  https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0005-bidir-constr-sigs.rst David FeuerWell-Typed, LLP Original message From: Matthew Pickering Date: 1/15/18 3:27 PM (GMT-05:00) To: David Feuer

Re: Implementing pattern synonym constructor signatures

2018-01-15 Thread Matthew Pickering
What is a constructor signature? Where is this specified? On Mon, Jan 15, 2018 at 7:10 PM, David Feuer wrote: > Over the past week I've started digging into the code that implements > pattern synonyms with an eye toward implementing the pattern synonym > construction

Implementing pattern synonym constructor signatures

2018-01-15 Thread David Feuer
Over the past week I've started digging into the code that implements pattern synonyms with an eye toward implementing the pattern synonym construction function signature proposal. I think I understand a decent amount of what's going on most places. However, I don't understand enough about type

Re: Release policies

2018-01-15 Thread Boespflug, Mathieu
[replying to ghc-devops-group@, which I assume based on your email's content is the mailing list you intended.] Hi Simon, feedback from downstream consumers of Cabal metadata (e.g. build tool authors) will be particularly useful for the discussion here. Here are my thoughts as a bystander. It's

cvs-ghc mailing list dead?

2018-01-15 Thread Steven Shaw
This email list appears to be dead but I figured it might forward to ghc-devs . Just checking... ___ ghc-devs mailing list