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

Consider missing signature equivalent to non-generic one #696

Conversation

raboof
Copy link
Contributor

@raboof raboof commented Apr 13, 2022

Since for those it should be sufficient to check the descriptor anyway,
and the Scala compiler started emitting more signatures between
3.1.1 and 3.1.2

Fixes #693

Since for those it should be sufficient to check the descriptor anyway,
and the Scala compiler started emitting more signatures between
3.1.1 and 3.1.2

(from the functional tests it seems there were already a couple
of cases where Scala3 produced more signatures than expected, we now
ignore those as well)

References lightbend-labs#693
@raboof raboof force-pushed the consider-missing-signature-equivalent-to-nongeneric branch from ab786c4 to 6e017db Compare April 13, 2022 18:12
@raboof
Copy link
Contributor Author

raboof commented Apr 13, 2022

hmm, testFunction shows I missed a spot, have to look into this later

ah, scala3 previously already generated 'unexpected' signatures in some cases already (scala/scala3#10837), these problems are also filtered out with this approach. That seems OK.

@raboof raboof marked this pull request as ready for review April 13, 2022 18:14
@raboof raboof requested a review from dwijnand April 29, 2022 07:18
@lefou
Copy link
Contributor

lefou commented Sep 8, 2022

Can we get a new release containing this fix?

@SethTisue
Copy link
Collaborator

Can we get a new release containing this fix?

Dale's on vacation at the moment. Though little of his attention has been going to MiMa lately

I note that this repo isn't on sbt-ci-release. Releases would be easier to roll if it were.

I've opened #718 – perhaps a volunteer would like to tackle it

@SethTisue SethTisue added this to the 1.1.1 milestone Sep 16, 2022
@SethTisue
Copy link
Collaborator

1.1.1 is published

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.

Unexpected failed binary compatibility checks when upgrading Scala 3.x from 3.1.1 to 3.1.2
4 participants