Skip to content

Make erased value type take a TypeRef instead of a ClassSymbol #1199

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 6, 2016

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Apr 3, 2016

To address #1198, we need to avoid putting symbols in ErasedValueTypes.
Fixes #1198.

Review by @VladimirNik.

To address scala#1198, we need to avoid putting symbols in ErasedValueTypes.
@smarter
Copy link
Member

smarter commented Apr 3, 2016

Wait, how come an ErasedValueType ends up existing in multiple runs? They should only exist between Erasure and ElimErasedValueType

@@ -69,17 +69,17 @@ object TypeErasure {
* @param cls The value class symbol
Copy link
Member

Choose a reason for hiding this comment

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

param doc needs to be updated

@odersky
Copy link
Contributor Author

odersky commented Apr 3, 2016

@smarter

Wait, how come an ErasedValueType ends up existing in multiple runs? They should only exist between Erasure and ElimErasedValueType

I believe it's as a result of an InfoTransformer.

@smarter
Copy link
Member

smarter commented Apr 3, 2016

Should we run more tests like the dotty test with twice to catch this kind of bug?

@VladimirNik
Copy link
Contributor

LGTM

@odersky odersky merged commit 1a6eedd into scala:master Apr 6, 2016
@allanrenucci allanrenucci deleted the fix-stale-sym branch December 14, 2017 19:21
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.

4 participants