Skip to content

Add exe ghc-supported-languages#11634

Open
philderbeast wants to merge 3 commits intohaskell:masterfrom
cabalism:exe/ghc-supported-languages
Open

Add exe ghc-supported-languages#11634
philderbeast wants to merge 3 commits intohaskell:masterfrom
cabalism:exe/ghc-supported-languages

Conversation

@philderbeast
Copy link
Collaborator

@philderbeast philderbeast commented Mar 18, 2026

Fix for #11633.

Note

Should we move this module to cabal-dev-scripts?

Current output:

$ ghc --numeric-version
9.14.1

$ which ghc | xargs cabal run Cabal-tests:lang-tests
Warning: this is a debug build of cabal-install with assertions enabled.
The following extensions are known to GHC but are not in the 
extension registry in Language.Haskell.Extension.
  Haskell98
  Haskell2010
  GHC2021
  GHC2024
  ExplicitLevelImports
  NoExplicitLevelImports
  ImplicitStagePersistence
  NoImplicitStagePersistence
If these extensions are ready for public consumption then they 
should be registered. If they are still experimental and you 
think they are not ready to be registered then please add them 
to the exceptions list in this test program along with an 
explanation.

, "extension registry in Language.Haskell.Extension."
, " " ++ intercalate "\n " (map display unregistered)
, "If these extensions are ready for public consumption then they "
, "should be registered. If they are still experimental and you "
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GHC has a specific notion of "experimental" for extensions whose semantics is not entirely set in stone. It is not an excuse for Cabal not to recognise them, so I think the wording here is confusing.

If an extension is available from a released GHC (or would be available soon as witnessed by an alpha release or RC), it must be recognised by Cabal, that's it. If one is testing an experimental build of GHC (such as GHC HEAD), the extension could remain unrecognised by Cabal for time being. Could you simplify the message to this effect?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you simplify the message to this effect?

Happy to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants