-
Notifications
You must be signed in to change notification settings - Fork 102
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
add Scala 3 to crossbuild #215
Conversation
this is already handled by sbt-scala-module
I do not fully understand why this was here, but Scala 3 was complaining: "Polymorphic refinement method valueStepper without matching type in parent trait MapOps is no longer allowed" simplifying the code as I have done in this commit compiles on both Scala versions and the tests still pass, and this is an obscure enough corner of the API that I'm not inclined to spend time really digging deeply into it (e.g. attempting to construct a test case that would now compile when it shouldn't, or vice versa)
This was routine work, with one exception, which I isolated in its own commit: 5160b41, which removes a type parameter which I couldn't figure out how to make Scala 3 accept ("Polymorphic refinement method valueStepper without matching type in parent trait MapOps is no longer allowed") ...but I also don't really understand under what circumstances it might matter and I'm not inclined to spend time really digging into it without some external indication that it's important @Ichoran Do you by any chance remember what that |
I'm going to go ahead and merge this so we can roll 1.0.0-RC1 for Scala 3.0.0-RC2. Still happy to receive feedback, post-merge. |
fixes #200