-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Dotty cannot read Scalac @specialized annotations #205
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
Ouch. It looks like the Unpickler has to invoke resolveOverloaded to get to the right constructor. That's not nice at all, but I do not see a better alternative. |
I was able to reuse This rises a question of should positions be set for annotation trees read from bytecode or not. As those trees aren't representing a code that is in control of user I would say that any synthetic position should be ok. @odersky, Do you have a better idea? |
Good that resolveOverloaded works. I don't see right now how narrowByTrees On Wed, Oct 29, 2014 at 9:47 PM, Dmitry Petrashko [email protected]
Martin Odersky |
should be fixed in #206 |
https://github.com/lampepfl/dotty/blob/master/src/dotty/tools/dotc/core/pickling/UnPickler.scala#L829
Dotty always assumes that default constructor of annotation is called. That's not true for common case of
@specialized(Int)
.The text was updated successfully, but these errors were encountered: