You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Right now, if you specify user namespaces in configuration.edn with the
:export-namespaces
key, they will be AOT'd when theAOT
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:
configuration.edn
for AOT'ing user namespaces specificallyThe text was updated successfully, but these errors were encountered: