Fix renaming of classes in presence of generic signatures and nested classes. #299
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 is a possible fix for issue #298 that allows to rename a class and its nested classes in presence of generics. If for example we consider the following class:
the fix allows, e.g., to rename the class
a.b.C
top.q.R
and keep unchanged the names of the nested classes as follows:I am not sure that this semantics complies with the meant one for Javassist.