Hi, the distiction between an issue and a pull request is a rather thin one, and the Github API actually allows you to upgrade an issue to a pull request…
So no need to be picky about the precise form: If someone has something interesting to say in an issue without yet having some text to attach to it, by all means go for it! Cheers, Joachim Am Dienstag, den 01.05.2018, 15:23 -0400 schrieb Richard Eisenberg: > 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 -- Joachim Breitner m...@joachim-breitner.de http://www.joachim-breitner.de/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
