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

Backport "Heal occurrences of => T between ElimByName and Erasure" to LTS #20871

Merged
merged 2 commits into from
Jul 1, 2024

Conversation

WojciechMazur
Copy link
Contributor

Backports #19558 to the LTS branch.

PR submitted by the release tooling.
[skip ci]

odersky added 2 commits June 28, 2024 18:38
There's a window of vulnerability between ElimByName and Erasure where some
ExprTypes `=> T` that appear as parameters of function types are not yet converted
to by-name functions `() ?=> T`. These would cause an assertion violation when
used as operands of & or |. We fix this on the fly when forming these types in TypeComparer.
As explained in ElimByName, we can't fix it beforehand by mapping all occurrences of `=> T` to
`() ?=> T` since that could lead to cycles.

Fixes #19548

[Cherry-picked 1ea4c86]
Avoids follow-up failures in Ycheck for the test case.

[Cherry-picked 278beb8]
Base automatically changed from lts-19464 to lts-3.3 July 1, 2024 08:30
@WojciechMazur
Copy link
Contributor Author

No regressions detected in the community build up to lts-19605.

Reference

@WojciechMazur WojciechMazur merged commit a462528 into lts-3.3 Jul 1, 2024
19 checks passed
@WojciechMazur WojciechMazur deleted the lts-19558 branch July 1, 2024 08:30
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.

2 participants