Skip to content

Fix unpickling of match type aliases #11340

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

Merged
merged 1 commit into from
Feb 10, 2021
Merged

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Feb 7, 2021

We missed a cyclic check for them, which meant that no LazyRefs
were inserted that would prevent stackoverflows in subsequent operations.

Fixes #11250

The fix was simple but it took a while to figure out what was wrong.

We missed a cyclic check for them, which meant that no LazyRefs
were inserted that would prevent stackoverflows in subsequent operations.
@odersky
Copy link
Contributor Author

odersky commented Feb 7, 2021

test performance please

@dottybot
Copy link
Member

dottybot commented Feb 7, 2021

performance test scheduled: 2 job(s) in queue, 1 running.

@dottybot
Copy link
Member

dottybot commented Feb 8, 2021

Performance test finished successfully:

Visit http://dotty-bench.epfl.ch/11340/ to see the changes.

Benchmarks is based on merging with master (16bf86f)

@odersky odersky merged commit 16170a5 into scala:master Feb 10, 2021
@odersky odersky deleted the fix-11250 branch February 10, 2021 18:39
@Kordyjan Kordyjan added this to the 3.0.0 milestone Aug 2, 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.

Aliases to Tuple match types types and separate compilation
4 participants