Starting from Scala 2.13.2, it is no longer allowed to define an inner class with the same name as an inner class in the super class of the outer: https://github.com/scala/bug/issues/8353
As context-applied generates such class names when you extend a class which has a context bound with the same name, it generates a warning, for example in https://github.com/profunktor/redis4cats/issues/244. This PR fixes that by appending the outer class' name to make it unique.
Includes as well:
Update Scala to 2.13.1
Update kind-projector to 0.11.0
To reproduce the problem itself, do the following:
Fix kind-projector to "org.typelevel" % "kind-projector_2.13.1" % "0.11.0"
Open a sbt session
set ThisBuild/resolvers += "scala-integration" at "https://scala-ci.typesafe.com/artifactory/scala-integration/"
Starting from Scala 2.13.2, it is no longer allowed to define an inner class with the same name as an inner class in the super class of the outer: https://github.com/scala/bug/issues/8353
As context-applied generates such class names when you extend a class which has a context bound with the same name, it generates a warning, for example in https://github.com/profunktor/redis4cats/issues/244. This PR fixes that by appending the outer class' name to make it unique.
Includes as well:
To reproduce the problem itself, do the following:
"org.typelevel" % "kind-projector_2.13.1" % "0.11.0"
set ThisBuild/resolvers += "scala-integration" at "https://scala-ci.typesafe.com/artifactory/scala-integration/"
++2.13.2-bin-53ba87a!
compile
- fails on the new test inshadowed.scala