Inconsistent type alias expansion #8
Comments
carymrobbins
added a commit
that referenced
this issue
Feb 27, 2018
scalac is deciding to expand our type alias in some cases, breaking things like implicit resolution. See scala/bug#10750
carymrobbins
added a commit
that referenced
this issue
Feb 27, 2018
carymrobbins
added a commit
that referenced
this issue
Feb 27, 2018
carymrobbins
added a commit
that referenced
this issue
Feb 27, 2018
Brings together both of our changes for resolving refs #8 which also includes my introduction of cats-tests
carymrobbins
added a commit
that referenced
this issue
Feb 27, 2018
…abstract-type Resolve conflicts from @joroKr21's and @carymrobbins' work for #8
carymrobbins
added a commit
that referenced
this issue
Feb 27, 2018
Fixes solution from @joroKr21 to support Scala 2.10
carymrobbins
added a commit
that referenced
this issue
Feb 27, 2018
|
Fixed in release 0.3.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems that encoding newtypes with a "normal" type alias means that scalac can expand it at will. We need to change the encoding from
type Type[..] = Base with Tag[..]to
type Type[..] <: Base with Tag[..]See scala/bug#10750
The text was updated successfully, but these errors were encountered: