-
Notifications
You must be signed in to change notification settings - Fork 31
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
newsubtype #14
newsubtype #14
Conversation
2758733
to
66b7372
Compare
66b7372
to
58fccd1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, I didn't think you would implement this so quickly 👍
case (Nil, false) => q"type Type <: Base with Tag" | ||
case (tparams, false) => q"type Type[..$tparams] <: Base with Tag[..$tparamsNames]" | ||
case (Nil, true) => q"type Type = Base with Tag" | ||
case (tparams, true) => q"type Type[..$tparams] = Base[..$tparamsNames] with Tag[..$tparamsNames]" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't this lead to problems with type inference again? What do we gain from using =
instead of <:
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this was the result of me thinking that the abstract type was causing boxing, but later I realized boxing was happening for a different reason (which you commented on as well -
scala/bug#10770).
Just added a commit to fix this and all looks good, nice catch!
Thanks to @joroKr21 for pointing this out #14 (comment)
39a1fd5
to
2889577
Compare
No description provided.