Skip to content

Conversation

@szeiger
Copy link
Contributor

@szeiger szeiger commented Aug 15, 2018

It exists only for cross-compiling the library between Scala 2 and Dotty
and is not supposed to be used directly.

@scala-jenkins scala-jenkins added this to the 2.13.0-RC1 milestone Aug 15, 2018
@szeiger szeiger modified the milestones: 2.13.0-RC1, 2.13.0-M5 Aug 15, 2018
@SethTisue SethTisue modified the milestones: 2.13.0-M5, 2.13.0-RC1 Aug 15, 2018
@SethTisue
Copy link
Member

[test] !!  948 - run/t3346e.scala                          [compilation failed with 0 errors]
[test] ##### Log file '/home/jenkins/workspace/scala-2.13.x-validate-main@3/test/files/run/t3346e-run.log' from failed test #####
[test] 
[test] t3346e.scala:8: error: not found: type AnyConstr
[test]   def quickSort[T](implicit ev0: Coll => SeqOps[T, AnyConstr, Iterable[T]],

@SethTisue
Copy link
Member

@smarter is there a need to get this into M5, or is RC1 okay?

It exists only for cross-compiling the library between Scala 2 and Dotty
and is not supposed to be used directly.
@szeiger szeiger force-pushed the issue/private-anyconstr branch from 6ed3b35 to 7e8242a Compare August 15, 2018 20:08
@szeiger
Copy link
Contributor Author

szeiger commented Aug 15, 2018

We shouldn't expose scala.collection.AnyConstr in M5 to keep our options open for RC1. That's what this PR is for.

@szeiger szeiger modified the milestones: 2.13.0-RC1, 2.13.0-M5 Aug 15, 2018
@SethTisue SethTisue self-assigned this Aug 15, 2018
@lrytz lrytz merged commit 44a66d6 into scala:2.13.x Aug 16, 2018
szeiger added a commit to szeiger/scala that referenced this pull request Dec 7, 2018
This also provides a nice solution for AnyConstr (see
scala#7077 and
scala#7072): We simply don’t need it
anymore.
szeiger added a commit to szeiger/scala that referenced this pull request Dec 11, 2018
This also provides a nice solution for AnyConstr (see
scala#7077 and
scala#7072): We simply don’t need it
anymore.

We really want to constrain both IterableCC and MapCC to Iterable
(the latter because it’s needed for MapView) but that causes collisions
after erasure, so we have to go back to IterableOnce for IterableCC.
Using something more specific (like MapOps with Iterable) for
MapCC is not possible because in MapView the MapCC is not actually
MapView but only View.
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