Implementors for deprecated exports?
Simon Peyton Jones
simon.peytonjones at gmail.com
Tue Nov 29 22:51:22 UTC 2022
Just to say: this is part of an effort (by the Stability Working Group) to
help us, as a community, walk the line between stability (which is
essential for Haskell to be useful) and dynamism (which is essential for
Haskell to be truly alive).
It's not an easy line to walk (you can see meeting notes here)
there are quite a few things we can do to avoid unnecessary breakage and
Everything takes work, though, hence this invitation for contributions.
Please consider helping. But in a wider sense, if you have ideas relevant
to the scope of the Working Group
<https://github.com/haskellfoundation/stability>, do talk to us.
On Tue, 29 Nov 2022 at 20:50, David Christiansen <david at haskell.foundation>
> Dear GHC developers,
> The HF's Stability Working Group (
> https://github.com/haskellfoundation/stability) has been looking into
> ways to help Haskell developers maintain their code in the face of changes
> to the language and libraries.
> Out of the ideas we found, one is already an accepted GHC proposal, just
> waiting for implementation! This is adding the ability to deprecate an
> export, rather than just a definition, which would allow a function to be
> moved to a new home, with the old location re-exporting it under a
> deprecation warning for a few releases.
> We're wondering: do any of you feel inspired to implement this? If you
> did, we'd do our best to make sure that you are supported with design
> advice and code review. This is probably not a good first contribution to
> GHC; you'll need some familiarity with GHC and how to build it.
> The accepted proposal is here:
> The GHC ticket that it emerged from is here:
> All the best,
> David and Simon
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ghc-devs