[ghc-steering-committee] Proposal #569: multiline string literals; Rec: accept
Eric Seidel
eric at seidel.io
Sun Jan 21 18:28:15 UTC 2024
SimonM, Vlad,
The rest of the committee has expressed support for this proposal either on the ML or on SimonPJ's Google Sheet[1].
I think that is sufficient consensus to accept, but would prefer to get the full committee on record.
Please take a few minutes to read the proposal and record your vote. Barring any explicit dissent, I will mark the proposal accepted next weekend.
Eric
[1]: https://docs.google.com/spreadsheets/d/1e6GdwHmAjeDEUhTvP-b18MDkpTfH3SMHhFu5F3nDIWc/edit?usp=sharing
On Mon, Jan 15, 2024, at 02:21, Arnaud Spiwack wrote:
> On Sat, 13 Jan 2024 at 21:42, Adam Gundry <adam at well-typed.com> wrote:
>> On the meta point, I agree with Simon's position here: we should avoid
>> giving unconditional acceptance to underspecified proposals, only to
>> potentially discover problems later. But where a proposal is not
>> precisely specified, it would be preferable to accept in principle (so
>> the author is not left wondering whether the idea has a chance) and then
>> ask and support the author to finish the spec before merging the PR.
>
> I agree too. I was thinking about it over the weekend: we kind of need
> a status to say “we pretty much know we're going to accept it, so go
> ahead and do the implementation, but we're still working the details
> out together” (I was thinking in particular of the choice of string
> delimiters from this proposal: it makes no material difference to the
> implementation what we eventually settle on. So if there are questions,
> we should avoid holding the implementation effort back just because
> we're having a discussion about what we think it best).
> _______________________________________________
> ghc-steering-committee mailing list
> ghc-steering-committee at haskell.org
> https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee
More information about the ghc-steering-committee
mailing list