Add exe ghc-supported-languages#11634
Conversation
fefc2b7 to
629050f
Compare
0a3f2b2 to
32cccd1
Compare
b3e1c7a to
181e4c4
Compare
88b9e3f to
a861deb
Compare
No, because it needs the development version of cabal/Cabal-syntax/src/Language/Haskell/Extension.hs Lines 125 to 130 in ec8052b |
- Format ghc-supported-languages module - Add an args check with help - All extensions should be registered - Exclude known languages - Rename exceptions to langsAsExts - Rename executable to ghc-supported-extensions - Use explicit import lists, except for prelude - Don't use dieNoVerbosity - Move to exes/GhcSupportedExtensions.hs - Handle the zero args case gracefully - Satisfy fourmolu - We're checking KnownExtension - Avoid _ in registered pattern match - Mention language editions - Add a note about missing language editions
4578b9a to
82823b4
Compare
|
I added a check for language extensions to the preflight section of the release checklist. |
|
FWIW that was already there, indirectly, via checking for new options. But nobody ran that for 3.16, because @wz1000 told us there weren't any. Sadly, I'm pretty sure Zubin was thinking |
I think I found what you mean, each GHC release also has its own cabal issue with a checklist, such as #9729. |
|
Actually, it looks like someone reverted it at some point. It included a shell recipe for comparing (And now it's out of my shell history, sadly.) |
|
Okay, re-added it just after yours. The original version also checked |
Merge Queue Status
This pull request spent 1 hour 52 minutes 40 seconds in the queue, including 1 hour 42 minutes 4 seconds running CI. Required conditions to merge
|
Fix for #11633.
Note
Should we move this module to
cabal-dev-scripts?Manual QA Notes
Test with various GHC versions.
significance: significantin the changelog file.