[ghc-steering-committee] GHC2024 committee deliberation

[Simon Peyton Jones]

>
> So where do we stand?
>


   - I'm happy for us to define GHC2024 now.

   - I do not feel strongly about the exact list of extensions... for me
   this is very user-driven.

   - 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?

   - 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.

   - 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.

   - Other extensions are "big": MonoLocalBinds and TypeFamilies in
   particular.   I'm OK with including them>


   - 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!

Simon




On Thu, 30 Nov 2023 at 18:30, Joachim Breitner <mail at joachim-breitner.de>
wrote:

> Hi all,
>
> Am Mittwoch, dem 22.11.2023 um 22:11 +0100 schrieb Joachim Breitner:
> > Am Mittwoch, dem 22.11.2023 um 21:25 +0100 schrieb Joachim Breitner:
> > > I guess I could at least do a simple poll on discourse with the
> > > currently proposed extensions.
> >
> > Now at https://discourse.haskell.org/t/ghc2024-community-input/8168.
> > Not perfect (e.g. number of options on Discourse are limited), but it’s
> > something.
>
> after a week, we got 137 people to vote. This is of course not
> representative of our full target audience, but still useful input. For
> example, I didn’t expect LambdaCase to be that popular (84%). Other
> interesting bits:
>
>  * DerivingVia is the most popular extension that we do _not_ have
>    on the ballot for 2024, with 62%.
>    I think it's reasonable, I woudn’t mind maturing it a for another
>    edition cycle or so; there was talk about improving error messages.
>
>  * Lots of discussion about BlockArguments, but mostly along the lines
>    of “I use it (in Haskell or other languages), it’s great” vs.
>    “It don’t use it, it looks weird to me.”. My hypothesis is that
>    it is no harder to get used to than application-by-juxtaposition
>    or $ or other keywords, so I’m still in favor.
>
> Anyways, have a look if you are curious, and take it into account in
> your voting if I want.
>
>
> So where do we stand? Does everyone in the committee have the
> information they need to cast a vote? Should we just go ahead with
> voting, or would some committee members maybe share an assessment of
> the currently proposed extensions at
>
> https://github.com/ghc-proposals/ghc-proposals/blob/joachim/ghc2024/proposals/0000-ghc2024.rst
> to help people decide?
>
> Cheers,
> Joachim
>
>
>
>
>
> --
> Joachim Breitner
>   mail at joachim-breitner.de
>   http://www.joachim-breitner.de/
>
> _______________________________________________
> ghc-steering-committee mailing list
> ghc-steering-committee at haskell.org
> https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-steering-committee/attachments/20231204/bdad8325/attachment.html>