BUG: TermRefs with uninstantiated type variables get incorrect signatures #822
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR should not be merged, it demonstrates a bug.
After
frontend
,pickleinf.scala
looks like:The bug only manifests itself after unpickling, but the problem is already present when we pickle the type:
Notice that in the signature we get
java.lang.Object
instead ofscala.Int
for the first parameter and the return type, this happens because the signature is computed and cached beforeN
is instantiated toInt
.CC @odersky