I like this idea, but I think this can be done as a PR, which seems a better fit for collaborative building. The author can specify that a proposal is a "pre-proposal", with the goal of fleshing it out before committee submission. If it becomes necessary, we can furnish a tag to label these, but I'm honestly not sure we'll need to.
Richard > On May 1, 2018, at 2:24 PM, David Feuer <david.fe...@gmail.com> wrote: > > Sometimes, a language extension idea could benefit from some community > discussion before it's ready for a formal proposal. I'd like to propose that > we open up the GitHub issues tracker for ghc-proposals to serve as a place to > discuss pre-proposal ideas. Once those discussions converge on one or a few > specific plans, someone can write a proper proposal. > _______________________________________________ > ghc-devs mailing list > ghc-devs@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
