-
Notifications
You must be signed in to change notification settings - Fork 701
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
virtual-modules section: docs #7602
Comments
That's just a flat list of modules, just as exposed-modules. Some snippets from Cabal/ChangeLog.md: * Added doc/cabal-package.rst:.. pkg-field:: virtual-modules: identifier list |
TL;DR you don't need |
Cheers Mikolaj, Oleg. So for all practical purposes could this file be added in ghc-prim/GHC folder to the same effect: Background:GHC.Prim is imported in a few places. A custom (editor) name resolver does not find GHC.Prim when viewing / editing GHC sources. |
@ciez no. That would be a different module. It also may confuse build system, if source existed. -- special case for GHC.Prim; we won't find it in the filesystem.
-- This is important only when compiling the base package (where GHC.Prim
-- is a home module).
if mod `installedModuleEq` gHC_PRIM
then return (InstalledFound (error "GHC.Prim ModLocation") mod)
else searchPathExts home_path mod exts |
So in this particular case, what Haskell (apart from C, C++) symbols does GHC.Prim export? All the symbols exported by |
The haddocks are correct. (EDIT: They are magically generated, that's why they don't exist for ghc-prim-0.7 on hackage). The primitive types like |
Cheers Oleg! Appreciate this. |
Could anyone hint / share links to a description of .cabal file virtual-modules section?
The docs show but a placeholder:
https://cabal.readthedocs.io/en/3.4/cabal-package.html?highlight=virtual-modules#pkg-field-virtual-modules
The text was updated successfully, but these errors were encountered: