Skip to content

Fix #3480: Fix expanded name #3491

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
Nov 20, 2017
Merged

Fix #3480: Fix expanded name #3491

merged 1 commit into from
Nov 20, 2017

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Nov 16, 2017

Expanded name behaved different from what would be expected
by the fullNameSeparated conventions. This led to local
dummies creeping in the expanded names for local definitions
in templates.

Expanded name behaved different from what would be expected
by the fullNameSeparated conventions. This led to local
dummies creeping in the expanded names for local definitions
in templates.
@odersky odersky requested a review from smarter November 16, 2017 16:36
Foo$$init$$$bar$1
Foo$$init$$$bar$2
Bar$$init$$$bar$1
Foo$$_$bar$1
Copy link
Member

Choose a reason for hiding this comment

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

Why was this changed? Isn't this going to make debugging more difficult?

Copy link
Contributor Author

@odersky odersky Nov 17, 2017

Choose a reason for hiding this comment

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

It makes things more regular. Fully qualified names in general represent terms in the owner chain with "_$". The problem was that we treated the last separator of an expanded name as different from the others. This looks wrong. It's a different question what fully qualified names should do to represent term owners in the chain. AFAIK scalac skips them completely.

@odersky odersky merged commit ecfc9ef into scala:master Nov 20, 2017
@allanrenucci allanrenucci deleted the fix-#3480 branch December 14, 2017 19:19
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