Ignore when first constructor parameter is dropped from Signature #378
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.
Before Scala 2.12.9/2.13.1, the
Signature
attribute of an inner classconstructor would also contain the first, synthetic parameter.
This was fixed in scala/scala#7975, which course leads
to mima warnings about inconsistent signatures. Since the descriptor remains
the same, and the previous signature was wrong anyway (so anything relying on
it can not have worked in the first place) this specific change can be safely
ignored
Tested with Akka HTTP, akka/akka-http#2655 (comment)