I am curious why folks are voting against BlockArguments? These days it and ImportQualifiedPost are the two extensions I turn on in pretty much any new project.
Greetings from an old member!I am curious why folks are voting against BlockArguments? These days it and ImportQualifiedPost are the two extensions I turn on in pretty much any new project.Is the thinking that it it will be removed in the future? That would be very unfortunate, as I use it a lot, and the change would affect a lot of code. If not, are folks concerned about some sort of error it might cause?I see zero benefit in having to write BlockArguments in the extension field of my Cabal file, but it's also not that onerous, so not a big deal, just curious.Happy new year!Iavor_______________________________________________On Wed, Jan 3, 2024, 03:21 Joachim Breitner <mail@joachim-breitner.de> wrote:Happy new year everyone!
Am Freitag, dem 08.12.2023 um 18:54 +0100 schrieb Joachim Breitner:
> Ballot boxes are upen until Jan 8th, but it is probably better for
> everyone if votes are casted sooner. Maybe we can do it within a week?
5 more days of voting, still waiting for the ballot from Moritz and
Chris.
So far, we have DerivingStrategies, DisambiguateRecordFields, GADTs
with MonoLocalBinds and LambdaCase are definitely in, and TypeData and
BlockArguments are definitely out.
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