<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="font-family:tahoma,sans-serif" class="gmail_default">
So where do we stand?
</div></blockquote><br><ul><li class="gmail_default" style="font-family:tahoma,sans-serif">I'm happy for us to define GHC2024 now.<br><br></li><li class="gmail_default" style="font-family:tahoma,sans-serif">I do not feel strongly about the exact list of extensions... for me this is very user-driven.<br><br></li><li class="gmail_default" style="font-family:tahoma,sans-serif">The votes were interesting. I would also love to see stats on extension usage, derived from trawling Hackage. I'm sure this has been done, probably many times. Do we have data?<br><br></li><li class="gmail_default" style="font-family:tahoma,sans-serif">Several features were suggested that got more votes than the ones currently in the GHC2024 proposal. Why exclude them from our committee voting? E.g. RecordWildCards seems popular.<br><br></li><li class="gmail_default" style="font-family:tahoma,sans-serif">Some extensions come down to taste. Personally I don't like `BlockaArguments` but clearly quite a lot of people do. So I don't really object.<br><br></li><li class="gmail_default" style="font-family:tahoma,sans-serif">Other extensions are "big": MonoLocalBinds and TypeFamilies in particular. I'm OK with including them></li></ul><div><ul><li><span class="gmail_default" style="font-family:tahoma,sans-serif">I would argue (mildly) against DefaultSignatures. It's a mature and stable extension, but a pretty tricky, speicalised and ad-hoc one. Data from usage in Hackage might affect my opinion!</span></li></ul><div><div style="font-family:tahoma,sans-serif" class="gmail_default">Simon</div><br></div></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 30 Nov 2023 at 18:30, Joachim Breitner <<a href="mailto:mail@joachim-breitner.de">mail@joachim-breitner.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi all,<br>
<br>
Am Mittwoch, dem 22.11.2023 um 22:11 +0100 schrieb Joachim Breitner:<br>
> Am Mittwoch, dem 22.11.2023 um 21:25 +0100 schrieb Joachim Breitner:<br>
> > I guess I could at least do a simple poll on discourse with the<br>
> > currently proposed extensions.<br>
> <br>
> Now at <a href="https://discourse.haskell.org/t/ghc2024-community-input/8168" rel="noreferrer" target="_blank">https://discourse.haskell.org/t/ghc2024-community-input/8168</a>.<br>
> Not perfect (e.g. number of options on Discourse are limited), but it’s<br>
> something.<br>
<br>
after a week, we got 137 people to vote. This is of course not<br>
representative of our full target audience, but still useful input. For<br>
example, I didn’t expect LambdaCase to be that popular (84%). Other<br>
interesting bits:<br>
<br>
* DerivingVia is the most popular extension that we do _not_ have<br>
on the ballot for 2024, with 62%.<br>
I think it's reasonable, I woudn’t mind maturing it a for another<br>
edition cycle or so; there was talk about improving error messages.<br>
<br>
* Lots of discussion about BlockArguments, but mostly along the lines<br>
of “I use it (in Haskell or other languages), it’s great” vs.<br>
“It don’t use it, it looks weird to me.”. My hypothesis is that<br>
it is no harder to get used to than application-by-juxtaposition<br>
or $ or other keywords, so I’m still in favor.<br>
<br>
Anyways, have a look if you are curious, and take it into account in<br>
your voting if I want.<br>
<br>
<br>
So where do we stand? Does everyone in the committee have the<br>
information they need to cast a vote? Should we just go ahead with<br>
voting, or would some committee members maybe share an assessment of<br>
the currently proposed extensions at<br>
<a href="https://github.com/ghc-proposals/ghc-proposals/blob/joachim/ghc2024/proposals/0000-ghc2024.rst" rel="noreferrer" target="_blank">https://github.com/ghc-proposals/ghc-proposals/blob/joachim/ghc2024/proposals/0000-ghc2024.rst</a><br>
to help people decide?<br>
<br>
Cheers,<br>
Joachim<br>
<br>
<br>
<br>
<br>
<br>
-- <br>
Joachim Breitner<br>
<a href="mailto:mail@joachim-breitner.de" target="_blank">mail@joachim-breitner.de</a><br>
<a href="http://www.joachim-breitner.de/" rel="noreferrer" target="_blank">http://www.joachim-breitner.de/</a><br>
<br>
_______________________________________________<br>
ghc-steering-committee mailing list<br>
<a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</a><br>
<a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee" rel="noreferrer" target="_blank">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><br>
</blockquote></div>