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

Simplify level fixing scheme #15936

Merged
merged 1 commit into from
Aug 30, 2022
Merged

Simplify level fixing scheme #15936

merged 1 commit into from
Aug 30, 2022

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Aug 30, 2022

Don't instantiate co- and contravariant inner type variables eagerly.
Lift them instead to the reference level, same as for invariant type variables.

Fixes #15934

Don't instantiate co- and contravariant inner type variables eagerly.
Lift them instead to the reference level, same as for invariant type variables.

Fixes scala#15934
@odersky
Copy link
Contributor Author

odersky commented Aug 30, 2022

This makes a different tradeoff to what we had before. It fixes the akka issue. Let's see whether it's uniformly better for the other tests as well.

Copy link
Member

@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.

SGTM. Were you going to run the big CB on this before merging?

@odersky
Copy link
Contributor Author

odersky commented Aug 30, 2022

@WojciechMazur should we run the big CB on this branch or merge and test later?

@WojciechMazur
Copy link
Contributor

@odersky We can run it with the Open CB, however, it's currently busy with checking the latest nightly to validate the recent CC merge into the main branch. It's also checking all projects. This means we should be able to get results on a Thursday evening, as the full run takes ~20h.
I think we can merge it now and fix it later. There's one more, not yet reproduced library that failed last time.

@odersky
Copy link
Contributor Author

odersky commented Aug 30, 2022

OK, I merge it now, and then we can see whether the other regression was fixed as well or whether there are new ones.

@odersky odersky merged commit 8504b8d into scala:main Aug 30, 2022
@odersky odersky deleted the fix-15934 branch August 30, 2022 21:25
@bishabosha
Copy link
Member

bishabosha commented Aug 31, 2022

does this fix need to wait until 3.2.1 @Kordyjan ? - It looks like the regression it fixes was post 3.2.0 so I guess not

@WojciechMazur
Copy link
Contributor

The regression found in zio/zio-query was also fixed by this PR

@Kordyjan
Copy link
Contributor

does this fix need to wait until 3.2.1 @Kordyjan ? - It looks like the regression it fixes was post 3.2.0 so I guess not

I'm not sure if I understand the question. If regression it fixes was introduced after 3.2.0 then it is ok that the fix will be published in 3.2.1

@Kordyjan
Copy link
Contributor

Afaik #15746 was never backported and is scheduled for 3.2.1.

We can backport this PR and #15746, but it would delay the 3.2.0 for another week.

@Kordyjan
Copy link
Contributor

Kordyjan commented Aug 31, 2022

And I remember we agreed that considering the potential impact of #15746 we want it merged at the beginning of the 3.2.1 cycle and not rush it into 3.2.0

@odersky
Copy link
Contributor Author

odersky commented Aug 31, 2022

I agree this is for 3.2.1

@Kordyjan Kordyjan added this to the 3.2.1 milestone Aug 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Typer regression introduced in #15746
5 participants