Skip to content

Ycheck that scala.Array is erazed to either Object or JavaArrayType. #1005

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 7 commits into from
Jan 4, 2016

Conversation

DarkDimius
Copy link
Contributor

Expected to fail and demonstrate a bug in erasure.

It should either be erased to j.l.Object or replaced by JavaArrayType.
@odersky
Copy link
Contributor

odersky commented Dec 21, 2015

@DarkDimius If you give a LGTM we can merge this one.

@odersky
Copy link
Contributor

odersky commented Jan 3, 2016

@DarkDimius you still need to review my last commits, then we can merge.

@DarkDimius DarkDimius self-assigned this Jan 3, 2016
@DarkDimius
Copy link
Contributor Author

LGTM

DarkDimius added a commit that referenced this pull request Jan 4, 2016
Ycheck that scala.Array is erazed to either Object or JavaArrayType.
@DarkDimius DarkDimius merged commit 4bca332 into scala:master Jan 4, 2016
odersky referenced this pull request in dotty-staging/dotty Feb 18, 2016
Previously, the implicit definitions were always ambiguous, which
is surely not right.
@allanrenucci allanrenucci deleted the ycheck-erasure-arrays branch December 14, 2017 19:25
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.

3 participants