Skip to content
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

Ignore when first constructor parameter is dropped from Signature #378

Merged

Conversation

raboof
Copy link
Contributor

@raboof raboof commented Aug 21, 2019

Before Scala 2.12.9/2.13.1, the Signature attribute of an inner class
constructor 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)

Before Scala 2.12.9/2.13.1, the `Signature` attribute of an inner class
constructor 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)
@raboof
Copy link
Contributor Author

raboof commented Aug 21, 2019

Could revert all the filters added in #369 🎉

Copy link
Collaborator

@dwijnand dwijnand left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wonderful. Thank you.

@dwijnand dwijnand added this to the 0.6.0 milestone Aug 22, 2019
@dwijnand dwijnand merged commit d726234 into master Aug 22, 2019
@dwijnand dwijnand deleted the ignoreWhenFirstConstructorParameterIsDroppedInConstructor branch August 22, 2019 10:06
@raboof raboof mentioned this pull request Sep 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants