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

Fix #6242: package objects leak members from Any and Object #6498

Merged
merged 1 commit into from
May 12, 2019

Conversation

smarter
Copy link
Member

@smarter smarter commented May 12, 2019

Now they're hidden, just like in Scala 2.

Now they're hidden, just like in Scala 2.
Copy link
Contributor

@odersky odersky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is the change necessary? We are moving away from package objects anyway, so why add some special checking for them?

@smarter
Copy link
Member Author

smarter commented May 12, 2019

See #6242, the current behavior is preventing existing libraries from being used correctly, and this change also affects top-level definitions since they're encoded as package objects too.

@odersky
Copy link
Contributor

odersky commented May 12, 2019

@smarter OK, we definitely want to support package objects named eq.

@odersky odersky merged commit 9df4dfb into scala:master May 12, 2019
@allanrenucci allanrenucci deleted the packageObj-methods branch May 12, 2019 19:26
@anatoliykmetyuk anatoliykmetyuk added this to the 0.15 Tech Preview milestone May 21, 2019
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.

None yet

3 participants