
[Please do not reply to this mail discussing individual proposals. Instead, reply to the appropriate thread, or start a new one.] Hi, we have now officially accepted Hex Floats https://github.com/ghc-proposals/ghc-proposals/pull/37 and rejected INCOMPLETE_CONTEXTS https://github.com/ghc-proposals/ghc-proposals/pull/34 Currently under discussion are: Constructor Synonyms and Pattern Synonym Signatures https://github.com/ghc-proposals/ghc-proposals/pull/41 https://github.com/ghc-proposals/ghc-proposals/pull/42 Shepherd: Chris Allen Proposal: Accept both Status: expecially the first one does not seem to attract consensus. Eval class https://github.com/ghc-proposals/ghc-proposals/pull/27 Shepherd: Richard Status: This came back after being sent to the author for revision. I guess at this point Richard should make a new decision suggestion. Also TODO (for Ben) Add @rleshchinskiy to the GitHub organization and remove @atzedijkstra https://github.com/orgs/ghc-proposals/people (or make me an owner there). Greetings, Joachim -- Joachim “nomeata” Breitner mail@joachim-breitner.de • https://www.joachim-breitner.de/ XMPP: nomeata@joachim-breitner.de • OpenPGP-Key: 0xF0FBF51F Debian Developer: nomeata@debian.org

| Constructor Synonyms and Pattern Synonym Signatures | https://github.com/ghc-proposals/ghc-proposals/pull/41 | https://github.com/ghc-proposals/ghc-proposals/pull/42 | Shepherd: Chris Allen | Proposal: Accept both | Status: expecially the first one does not seem to attract consensus. I don’t' think we should accept both: they clearly overlap. Even the author sees them as either/or. To me #42 seems fine, and desirably anyway; I prefer it to #41. Simon
participants (2)
-
Joachim Breitner
-
Simon Peyton Jones