-
Notifications
You must be signed in to change notification settings - Fork 691
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
cabal init does not always generate explicit export lists #9889
Comments
Hello and thanks for reporting! Not sure if it's useful to have the export list in Main specifically. But I guess if there's energy to fix it, that would be fine. |
It is especially important to add an export list to the main module, because it only has to export I still think omission of the explicit export list on the main module is a performance bug. |
This is the wrong thing to do if |
Is it even possible to import the Main module in another module? Even if that is possible, I think we can agree that 99% of packages don't do that. So I don't see the harm. |
Describe the bug
cabal init does not always generate explicit export lists. Export lists can be important for performance. Especially the
Main
module should always have an explicit export list that just exports themain
function.To Reproduce
Steps to reproduce the behavior:
(
--libandexe
has the same problem)That generates:
Expected behavior
It should generate:
System information
The text was updated successfully, but these errors were encountered: