Skip to content
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

No dedicated way to AOT user namespaces not for export #361

Closed
timsgardner opened this issue Apr 30, 2019 · 0 comments
Closed

No dedicated way to AOT user namespaces not for export #361

timsgardner opened this issue Apr 30, 2019 · 0 comments
Labels
API may require decisions about API documentation Issues relating to the wiki and docstrings

Comments

@timsgardner
Copy link
Contributor

Right now, if you specify user namespaces in configuration.edn with the :export-namespaces key, they will be AOT'd when the AOT menu item is selected (though there is nothing in the documentation to suggest this). However this leaves us without a story for namespaces that should be AOT'd but not exported.

This is pretty urgent, since AOT is of course the only way to avoid paying for compilation on startup.

We need to:

  • Provide an option in configuration.edn for AOT'ing user namespaces specifically
  • Explicitly document how this process works
@timsgardner timsgardner added API may require decisions about API documentation Issues relating to the wiki and docstrings labels Apr 30, 2019
@nasser nasser closed this as completed in b7f89c5 Jun 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API may require decisions about API documentation Issues relating to the wiki and docstrings
Projects
None yet
Development

No branches or pull requests

1 participant