-
Notifications
You must be signed in to change notification settings - Fork 232
null-safety: Need the ability to precompile executables that require experiments to be enabled #2504
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
Comments
FYI: adding a path override to a local copy of CC @jakemac53 |
FYI: given the change in behavior w/ |
Moving to the We need some mechanism for enabling pre-compilation of package executables that require experiments to be enabled - whether that is through the environment variable or some other mechanism. The reason you don't see this on some packages, or when adding a path dependency, is it doesn't attempt to precompile executables if the package it comes from depends on any path dependency (including the current package). So it works for any dependency of package:test. |
Actually now that I think about it this will likely be resolved by #2492. Feel free to close as a dupe if that is indeed the case. |
Closing this as a duplicate of dart-lang/sdk#41355 (which should probably be in the pub repo) I confirmed that the current commit for the (draft) PR #2493 does indeed fix the issue. I can run |
fails as follows for several null-safe migrations
See
null-safety
branches forvector_math
,clock
,fake_async
.Seeing this with
2.9.0-11.0.dev
– but with previous dev releases, too.pubspec.lock
The text was updated successfully, but these errors were encountered: