This all unfolded while I was laid flat by covid, but I would vote in favor of this proposal. I've seen sufficient evidence of folks unhappy with accepted-but-not-implemented proposals (most recently Matt Parsons about the modifiers proposal) that I think this would be an improvement.

That said, I think we should have broader support before accepting a proposal such as this.

Richard

On Oct 3, 2022, at 4:28 AM, Spiwack, Arnaud <arnaud.spiwack@tweag.io> wrote:

If we do come back to it, it's going to be stronger evidence that something in that space is needed.

On Mon, Oct 3, 2022 at 10:26 AM Simon Peyton Jones <simon.peytonjones@gmail.com> wrote:
As you say, it's not that big a deal.  I'm content to reject for now.  I'm sure we'll keep coming back to it!

Simon

On Sun, 2 Oct 2022 at 13:03, Joachim Breitner <mail@joachim-breitner.de> wrote:
Hi,

Am Dienstag, dem 20.09.2022 um 15:43 +0200 schrieb Joachim Breitner:
> So given that we don’t have a consensus, I suggest to not spend more
> time on it, let’s reject it (and remember where it is to be revived, if
> and when the problem becomes more clearer visible).

no complaints about this either? I’ll mark it as rejected in a few days
unless someone shouts.

Cheers,
Joachim

--
Joachim Breitner
  mail@joachim-breitner.de
  http://www.joachim-breitner.de/

_______________________________________________
ghc-steering-committee mailing list
ghc-steering-committee@haskell.org
https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee
_______________________________________________
ghc-steering-committee mailing list
ghc-steering-committee@haskell.org
https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee
_______________________________________________
ghc-steering-committee mailing list
ghc-steering-committee@haskell.org
https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee