Dear GHC devs, Your feedback is appreciated in a new proposal to streamline communication with the authors of the GHC API as GHC evolves [1].
The proposal aims to set a process to collect detailed information on how users depend on the GHC API, and how GHC developers think these dependencies should be adjusted when there are breaking changes. This proposal is related to the endeavor to stabilize the GHC API [2]. Although, rather than trying to define a stable API, it sets a process to deal with the current state of affairs where users depend on many unstable parts. Looking forward to your thoughts! Facundo [1] https://gitlab.haskell.org/ghc/ghc/-/issues/24096 [2] https://discourse.haskell.org/t/charting-a-course-toward-a-stable-api-for-ghc/7646 -- All views and opinions expressed in this email message are the personal opinions of the author and do not represent those of the organization or its customers. _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
