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
Make it easier to keep the compiler warm #2547
Comments
A reasonable request. This is definitely something I expected to add to the API. Mirrors will make this cleaner, but for now, we'll have to expose the library elements somehow. cc @gbracha. |
Added this to the M1 milestone. |
Removed this from the M1 milestone. |
Removed this from the Later milestone. |
Added this to the M2 milestone. |
Removed Priority-Medium label. |
Removed this from the M2 milestone. |
Added TriageForM5 label. |
Removed TriageForM5 label. |
Removed this from the Later milestone. |
Removed Oldschool-Milestone-Later label. |
The Dart2JS compiler gets cold at night. Whenever I want to use it it, it wakes from slumber newborn and needs to scan its built-in libraries. In the simple cases I'm playing with, this task takes more time than all of the other compilation tasks put together.
On my list of things to do, is to write another version of apiimpl.dart that allows me to pass in a state bundle of some form that includes all of the library elements. But if you could help do this it would make the API nicer to use for interactive purposes.
The text was updated successfully, but these errors were encountered: