-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
patched_dart2js_sdk has no _CompileTimeError class #29661
Comments
seems like this type just be declared in Basically, I don't expect fasta to know about anything that comes from individual patch implementations. |
That's one option. Another option is to make Fasta more flexible so the backend can choose how compile-time errors are reported. Similarly to how I added instantiateInvocation to VmTarget. |
Good point - I slightly prefer to avoid that if we can share the code in core lib, though. Mainly I'd like to be able to be able to produce kernel for dart2js or for ddc using the same target/options, which might require that at least those two platforms have the exact same Target (from package:kernel) and agree on a common place for CompileTimeError. To unblock you, here is a CL that just adds If we want to right away move towards that shared location, I like the idea of adding it to dart:_internal as a public class, instead of a private class in dart:core. Here is a CL that takes that approach: https://codereview.chromium.org/2897363002 I sent out the former CL, but decided to wait to hear from you before sending the latter (it has changes in the VM, so I rather bug them only if we agree on the direction) |
I agree. It's nicer to share library code. |
See #29661 for context R=ahe@google.com Review-Url: https://codereview.chromium.org/2901323002 .
submitted the simple fix for now |
The class
_CompileTimeError
is missing from patched_dart2js_sdk and leads to a crash. See #29660.The text was updated successfully, but these errors were encountered: