Skip to content

Fix #1284: Make classTag depend directly on erasure #1412

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
Jul 26, 2016

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Jul 25, 2016

In the end, a classTag reflects the erased version of a type. The only
condition for its generation should be that the erasure is stable under
possible instantiations.

In the end, a classTag reflects the erased version of a type. The only
condition for its generation should be that the erasure is stable under
possible instantiations.
@odersky
Copy link
Contributor Author

odersky commented Jul 25, 2016

Review by @xeno-by ?

return ref(defn.ClassTagModule)
.select(nme.apply)
.appliedToType(tp)
.appliedTo(clsOf(erasure(tp)))
Copy link

Choose a reason for hiding this comment

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

That's an interesting DSL! Does it cover the entire language, or it just contains a few most used utilities?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It covers about 30 ops, maybe half of them construct syntax trees. See ast.tpd#TreeOps for where it is defined.

@xeno-by
Copy link

xeno-by commented Jul 26, 2016

To the best of my knowledge, lgtm.

@odersky odersky merged commit 1b0315c into scala:master Jul 26, 2016
@allanrenucci allanrenucci deleted the fix-#1284 branch December 14, 2017 16:59
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