-
Notifications
You must be signed in to change notification settings - Fork 65
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
Transformer throws on admitSubtypeCapability #49
Comments
Thanks for spotting this! It is a bug when you get the 'Unexpected situation' exception (a fix will be included in the next commit), but it will not help you much: There is a rather detailed discussion about this capability in the design document https://github.com/dart-lang/reflectable/blob/master/reflectable/doc/TheDesignOfReflectableCapabilities.md which illustrates why the whole concept is questionable (and hence it might be dropped). However, if it would be very helpful for you then please make the case for it, and then we can keep your arguments in mind because they are on the issue list. PS: That would then be a new issue, because this one gets closed when the bug fix is available. |
I think @lassedamgaard mentions superclassQuantifyCapability, not admitSubtypeCapability. |
Sorry guys, wrong copy-pasta, the capability spec was supposed to say |
The error message for With respect to the diagnostic message: There is already issue #39 requesting a similar thing, namely that errors should be reported but then caught, such that the transformer can continue transforming the remaining entry points rather than stopping entirely. |
Addressed by commit 5a835be on https://github.com/dart-lang/reflectable/commits/master. |
Not sure if this capability is supposed to work in js, if not a better error message/guard should be provided.
This is the capability spec:
The text was updated successfully, but these errors were encountered: