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
more non-determinism in reflection #6826
Comments
Imported From: https://issues.scala-lang.org/browse/SI-6826?orig=1 |
@ghik said (edited on May 4, 2013 8:25:12 PM UTC): Below is what I found. I don't know if this is of any relevance or tells anything that isn't already obvious to you, Scala compiler guys, but I post this in case I save someone a little debugging time. In general, this seems to be a problem with lazy resolution of type associated with a Symbol.
This happened as a result of following call chain:
The innermost call ( OK, let's see what happens next:
Still the same...
Wrong result, that's a string representation of
Now the type seems to be correct.
Now that the symbol has correct type, everything's fine. |
@paulp said: Right, that's why it's called "unsafeTypeParams". Calling toString sometimes leads to normalize being called (that is a bug, which I might have fixed in master, can't remember) which can force the info. It's a big, complicated thing. |
This is really confusing behavior.
The text was updated successfully, but these errors were encountered: