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

Compiler introduces different symbols that have the same binary/internal name #6109

Closed
scabug opened this issue Jul 19, 2012 · 4 comments
Closed
Assignees
Labels
Milestone

Comments

@scabug
Copy link

@scabug scabug commented Jul 19, 2012

See:

https://groups.google.com/d/msg/scala-internals/Sg3xGKU6UWg/bNgDperR7acJ

I'm creating this ticket as place-holder so I can refer to it from other places. I'll provide more info later on.

@scabug

This comment has been minimized.

Copy link
Author

@scabug scabug commented Jul 19, 2012

Imported From: https://issues.scala-lang.org/browse/SI-6109?orig=1
Reporter: @gkossakowski
Affected Versions: 2.10.0
See #5954, #5957

@scabug

This comment has been minimized.

Copy link
Author

@scabug scabug commented Jul 19, 2012

@lrytz said:
I think this is not a bug.

The symbol loader will create a symbol for every classfile that it finds. See also [https://github.com/scala/scala/blob/21f14e371c0baa9d59678fe5645cea80586ef116/src/compiler/scala/tools/nsc/symtab/classfile/ClassfileParser.scala#L648]

@scabug

This comment has been minimized.

Copy link
Author

@scabug scabug commented Jul 19, 2012

@paulp said:
Stepping back, there are two possible approaches: don't create duplicate symbols in the first place, or detect duplicate symbols if they are created. I trust we all agree that the former approach is preferable wherever possible; but if it isn't (I don't know) then we would probably benefit from identifying some invariants about when/where/how we will encounter such duplicates and how/where/when we can reliably detect them.

@scabug scabug added the backend label Apr 7, 2017
@scabug scabug added this to the Backlog milestone Apr 7, 2017
@SethTisue

This comment has been minimized.

Copy link
Member

@SethTisue SethTisue commented Mar 2, 2018

closing stale backend tickets that may not be relevant in current Scala and seem unlikely to receive attention

@SethTisue SethTisue closed this Mar 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.