Re: [ghc-steering-committee] What should we start with?

I thought the Levity Polymorphism one (i.e, make the representation of unboxed tuples more fine grained) is a fairly straight one, so perhaps we should start with it? On Thu, Jan 19, 2017 at 9:53 AM, Christopher Allen wrote:

What's the most ready for discussion or implementation in your estimation?

...

Hi,

good to have a mailing list, thanks to whoever set it up.

I would like to see us warming up by handling a first proposal before all of us forget that we are on this committee. Which should we get started on?

There are two that have the “Pending review” label: Levity Polymorphism and OverloadedRecordFields https://github.com/ghc-proposals/ghc-proposals/ labels/Pending%20committee%20review According to our process documents, this label setting should have already triggered our part of the process!

We could also look for proposals that have not been updated in a while (you can sort by that in the issue list) for example * Optional tuple parenthesization <https://github.com/ghc-

...

* Stack pointer stuff <https://github.com/ghc-

On Wed, Jan 18, 2017 at 10:27 PM, Joachim Breitner wrote: proposals/ghc-proposals/pull/19> proposals/ghc-proposals/pull/17>

...

and others. I pinged a few random old proposals and asked them to maybe move forward (or abandon).

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 _______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee

-- Chris Allen Currently working on http://haskellbook.com _______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee