Dear GHC Steering Committee Proposal #601 <https://github.com/david-christiansen/ghc-proposals/blob/extension-lifecycle-proposal/proposals/0000-extension-lifecycle-framework.md> says We propose a categorization scheme for Haskell language extensions. This scheme is simple, in that there are few categories that are described in terms of the user-relevant aspects, and it is actionable, in that it suggests concrete changes to the warning system of GHC that allow users to express their own risk tolerance and get guidance as they upgrade their compiler I'm happy with this proposal: it seems simple, comprehensible, and actionable. The only question in my mind is whether it is worth the bother. I'd love to hear from the practitioners on the committee. But I propose that we accept it. Simon On Mon, 24 Jul 2023 at 14:39, Joachim Breitner <mail@joachim-breitner.de> wrote:
Dear Committee,
David Thrane Christiansen suggested to categorize extensions into Experimental, Mature, Deprecated and Legacy, and add warning flag to GHC that allow users to be warned about (or shouted at for) using such extensions, if they choose so.
https://github.com/ghc-proposals/ghc-proposals/pull/601
https://github.com/david-christiansen/ghc-proposals/blob/extension-lifecycle...
Because of the meta-like aspect of this proposal, I’d like to assign this to Simon PJ.
Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals#committee-process
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