Skip to content

Backport "Fix stack overflow errors when generating opaque type proxies" to 3.3 LTS #220

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
Apr 8, 2025

Conversation

tgodzik
Copy link

@tgodzik tgodzik commented Apr 7, 2025

Backports scala#22479 to the 3.3.6.

PR submitted by the release tooling.
[skip ci]

…22479)

Before the regressive PR, we would check via the generated opaqueProxies
list whether one was already generated. In that PR, we tried allowing
generating proxies for rhs of currently generated proxy. Since we have
to add the generated proxy to opaqueProxies only after that step, this
could cause infinite recursion (and adding the proxies earlier could
cause another infinite loop).

To fix that, we add another collection for termrefs which we already
visited this way, but which is not used in the `mapOpaques` function.
[Cherry-picked 6d9b0f1]
Base automatically changed from backport-lts-3.3-22446 to lts-3.3 April 8, 2025 17:44
@tgodzik
Copy link
Author

tgodzik commented Apr 8, 2025

No regressions detected in the community build up to backport-lts-3.3-22797.

Reference

@tgodzik tgodzik merged commit 579f2a6 into lts-3.3 Apr 8, 2025
22 checks passed
@tgodzik tgodzik deleted the backport-lts-3.3-22479 branch April 8, 2025 17:44
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