{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreige2ccfyequavqym4oycqcu6fxo7rrvluswfo6qqm4grkadw6ny5i",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3migo6fyikkk2"
  },
  "path": "/t/ghc-community-update-march-2026/13870#post_1",
  "publishedAt": "2026-04-01T10:28:28.000Z",
  "site": "https://discourse.haskell.org",
  "tags": [
    "our last post",
    "Call for Contributions of the last update",
    "“unrecognised warning flag” conceals cause by sanitizing incorrect syntax",
    "The existence of a file named “m” causes GHCI to fail.",
    "Confusing error message about type-like kinds when a type Type is in scope which is not the one from Data.Kind",
    "this is one that has been recently added",
    "There’s a new writeup about the plans and current state of Typed Template Haskell by Sheaf",
    "Should we adjust the bootstrapping policy to force bootstraipping to be possible with the latest LTS release?",
    "Release policy: Blockers/Delays for minor releases",
    "Coordinate testing of RCs with downstream distributors",
    "-XMultilineStrings does not permit literal tabs",
    "Don’t expose platform dependent interfaces from base",
    "@MangoIV",
    "https://ghc.gitlab.haskell.org/ghcup-metadata/ghcup-nightlies-0.0.7.yaml",
    "the Release Channels section on the GHCup docs",
    "@hasufell",
    "Check out this dashboard to find out when nightlies were last produced."
  ],
  "textContent": "Thank you for the positive feedback on our last post.\n\nThe GHC community update consists of three sections:\n\n  * **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.\n  * **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.\n  * **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.\n\n\n\n## Call for Contributions\n\nIn addition to the Call for Contributions of the last update we would appreciate your help on the following issues:\n\n  * “unrecognised warning flag” conceals cause by sanitizing incorrect syntax: GHC does some funny business when receiving a flag that looks like `-W=foo` – it reports it doesn’t know `-Wfoo`, even if it _does_ exist. Looks like a bug that might be a fun time to fix.\n  * The existence of a file named “m” causes GHCI to fail.: When the library search path is set incorrectly, GHC tries to read the library directly from the cwd. This is all fine, except that GHC barfs and panics if that file cannot be loaded. Perhaps we could improve the way GHC communicates this to the users.\n  * Confusing error message about type-like kinds when a type Type is in scope which is not the one from Data.Kind: GHC sometimes says “Expected a type, but ‘a’ has kind ‘Type’” – the ticket has the explanation what’s going wrong and also a proposal on how to fix it.\n  * And of course some issues with documentation, this is one that has been recently added\n\n\n\n## Call for Opinions\n\n  * There’s a new writeup about the plans and current state of Typed Template Haskell by Sheaf: If you are into staging, or just want to find out about the current state and plans of Typed Template Haskell or even have some time for a complicated but interesting project, have a read!\n  * Should we adjust the bootstrapping policy to force bootstraipping to be possible with the latest LTS release?\n  * Release policy: Blockers/Delays for minor releases: We are looking to make some minor adjustments to the release policy, more concretely, we’re wondering if preparing a new RC may be warranted to fix bugs on Tier 2 platforms. If you have opinions, please comment.\n  * Coordinate testing of RCs with downstream distributors: In the past we had some issues of bugs surfacing after a release had already been made. These could have been prevented by more extensive tests of the release candidates. While we’re looking into getting head.hackage, our own tool to catch such bugs, onto solid feet again, we would like to increase the coordination of release candidate testing and therefore work-sharing between distributors. Currently we’re looking to collaborate with stackage and nixpkgs but if you are a distributor building GHC and a lot of packages, please reach out!\n  * -XMultilineStrings does not permit literal tabs: Do you think they should? Please comment! If you feel strongly, perhaps you could even amend the existing proposal for evaluation by the ghc steering committee.\n  * Don’t expose platform dependent interfaces from base: Should base continue to be platform dependent? This is an important question in the ongoing efforts around reinstallable base.\n**Reminder** : The reinstallabe base effort will bring _huge_ improvements to the surface language but it’s a _ton_ of work. If you are excited for its benefits, we would be delighted about your help on that front. Please reach out to Teo Camarasu if you have some free cycles!\n\n\n\n## Maintainers’ Section\n\n  * **Nightlies are back on the menu!** I hope for longer this time. I (@MangoIV) will try to keep them being produced.\n    * The nightly ghcup yaml can be found at https://ghc.gitlab.haskell.org/ghcup-metadata/ghcup-nightlies-0.0.7.yaml\n    * Check out the Release Channels section on the GHCup docs for how to use them.\n    * TL;DR:\n\n          ghcup --url-source=https://ghc.gitlab.haskell.org/ghcup-metadata/ghcup-nightlies-0.0.7.yaml \\\n            list --show-nightly --since \"$(date -d \"last week\" -u +\"%Y-%m-%d\")\" -t ghc\n\n\n(thanks @hasufell for the correction)\n    * It would be very much appreciated to – if you have a complex or important library – set up a CI run that builds your library against the nightly, if your dependencies admit to that.\n    * Check out this dashboard to find out when nightlies were last produced.\n  * The forkoff for the next version of GHC, GHC 10.0.1 is going to happen next week. We will notify you on the usual channels.\n  * 10.0.1 will drop Tier 1 support for Debian 9 and 10 and Ubuntu 18 and 20. These are end of life distributions. We will not drop the support for x86_64 darwin, yet.\n\n",
  "title": "GHC community update March 2026"
}