Skip to content

Backport "Fail compilation if multiple conflicting top-level private defs/vals are in the same package" to 3.3 LTS #335

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 2 commits into from
Apr 27, 2025

Conversation

tgodzik
Copy link

@tgodzik tgodzik commented Apr 27, 2025

Backports scala#22759 to the 3.3.7.

PR submitted by the release tooling.
[skip ci]

jchyb and others added 2 commits April 27, 2025 12:52
…are in the same package (scala#22759)

Now the private top level definitions act basically the same as package
private (which is the same behavior as private objects/classes),
as that is what the reference implies, and it helps us avoid ambiguous
method/value selections.
…are in the same package (scala#22759)

Now the private top level definitions act basically the same as package
private (which is the same behavior as private objects/classes),
as that is what the reference implies, and it helps us avoid ambiguous
method/value selections.
[Cherry-picked 8fe16fe][modified]
@tgodzik
Copy link
Author

tgodzik commented Apr 27, 2025

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

Reference

@tgodzik tgodzik merged commit 3aee5f2 into lts-3.3 Apr 27, 2025
22 checks passed
@tgodzik tgodzik deleted the backport-lts-3.3-22759 branch April 27, 2025 18:57
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