Julien Richard-Foy

In my opinion this page does not contain a good example: https://docs.scala-lang.org/tour/abstract-type-members.html (what are the benefits compared to using a type parameter here?). It should be redesigned to use a...

@Shorla Thank you for proposing your help! We are currently (this is taking a bit of time, though…) reworking the Scala 3 reference documentation. In this context, it is probably...

That’s a good point, thank you for creating this issue. Would you be interested in submitting a fix?

I don't think we should systematically remove all the println statements. In the example you gave, that would improve the readability (although I would rename the val to 'message' instead...

Hey Ondrej, why do you nice varargs splice here? It seems `js.Dynamic.literal(s)` works?

We would need to - move the old collections guide to `/overviews/collections-2.12` - add a `redirect_from` directive to the “new” collections to make them available at `/overviews/collections`. That being said,...

Thank you for reporting. About the first point, I believe there should be a compatibility matrix showing which version of Scala 2.13 supports which version of Scala 3, in https://docs.scala-lang.org/scala3/guides/migration/compatibility-classpath.html#the-scala-213-tasty-reader....

For this case I'm not sure we want to apply this solution. Maybe it's better if the user changes its datatype to be an immutable.Seq from the beginning so that...

Bumping to 2.x will also create issues in projects that depend on 1.x in some way. However, I agree that we should initiate the migration at some point.

@gaopinghuang0 thank you for reporting. I agree with your comments. Would you be interested in contributing a pull request? Also, it is worth noting that in Scala 3 the trailing...