GHC community update Jan/Feb 2026

The GHC community update consists of three sections:

  1. Call for contributions: The GHC team asks for contributions - these range from issues that are simple and fun to solve to issues that require an expert pair of eyes that we have too few of.

  2. Call for opinions: The GHC team asks for your opinion on some matter regarding GHC - these are issues about often contentious matters where community input is highly valued. We ask that you engage in good faith.

  3. Maintainers’ section: To avoid surprises in upcoming GHC releases, we try to inform maintainers of Haskell libraries as early as possible to make sure they can test their libraries against unreleased GHC versions. This section is also relevant for industry users looking to adapt their codebases to newly released GHC versions.

Call for contributions

  • Searching for volunteers for reinstallable-base work: We are looking for contributors to the ongoing efforts on reinstallable base - @TeofilC has been doing a lot of work in that area, please contact him or comment under respective issues on the linked issue tracker.
  • Documentation issues: if you are a newcomer in GHC development but konw your way around as a user, these might be interesting first issues to tackle - more can be found at the GHC issue tracker
  • Add hints for TH level errors: The new level errors sometimes have unfortunate ergonomics - if you are a template-haskell user with good intuitition of these error messages, we would be happy about you adding hints to these error messages
  • Add hints when certain wired-in type classes cannot be solved for:
  • There are also a lot of issues wrt. improving error messages which are always a great improvement to the compiler - more can always be found on the issue tracker, filtered by newcomer

Call for opinions

Maintainers’ section

16 Likes

Thanks. This is great for transparency.

Two issues that I find significant for end users too:

4 Likes