Fix bug when shading ScalaLongSignature #10
Merged
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.
When shading a
@ScalaLongSignature(bytes = Array())
, ASM callsvisit()
for each item in the bytes array, and then callsvisitEnd()
for each timevisit()
was called as well.In visitEnd() we write the rewritten ScalaLongSignature completely, so this causes jarjar-abrams to write the ScalaLongSignature multiple times.
When reflecting on one of these classes, we get an error:
A decompilation of the affected class shows that the class is annotated multiple times with
@scala.reflect.ScalaLongSignature
.This fixes the issue by making sure we only call
rewriteAnnotation
once for the lifetime of the class. I tested this, and it solved the issue :)I imagine the issue wasn't caught earlier because running into this requires you to reflect/use typetags on very very large scala classes which have been rewritten by jarjar-abrams, which is likely rare.