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
support scala 2.13.7 #1493
support scala 2.13.7 #1493
Conversation
@@ -1,5 +1,5 @@ | |||
rules = [ | |||
ExplicitResultTypes, | |||
# ExplicitResultTypes, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[error] (rules / scalafixAll) scalafix.sbt.InvalidArgument: The ExplicitResultTypes rule only supports the exact Scala versions 'List(2.13.6, 2.13.4, 2.13.5)' for this binary version. To fix this problem, either remove ExplicitResultTypes from .scalafix.conf or change the Scala version of your build to match one of the supported versions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
make sense. we have to that everytime we upgrade the version!
I think we can comment the failing test and we will try to fix later. It doesn't seem to be too bad. thank for starting this! |
There are 2 tests failing, that were not failing with the Scalameta 4.4.29 update, and look related to compiler changes. 1/ scalafix/scalafix-tests/output/src/main/scala-2/test/explicitResultTypes/BetterRscCompat.scala Line 196 in 3b219fa
That seems related to https://github.com/scalameta/scalameta/pull/2502/files#diff-65b44c93ebcf284cd66432972b21ee5671b9ea3c1de809c400f7c8bc16b8041fR109-R115 2/
Not sure about this one... Any insight @tgodzik? |
might have to do with scala/scala#9712 ...? @som-snytt any other guesses? the backticked underscore is giving me a kind of Snytt-ish vibe or feeling of deja vu that I can't quite place |
|
Looks like As for 1) issue, in scalameta that was only an issue with tests, it did not cause any problems when using semanticdb as a normal compiler plugin. It might be the same case here. |
I'll refresh my memory about the change in handling wildcard. One progression was allowing multiple wildcards. I linked another change in behavior. Edit: the linked issue is not relevant. I see the relevant change is, yes, that fresh names are emitted for the underscores. I haven't had a chance to look at the test here yet. Dotty has a bit more support for these wildcard names. |
Does this bug means that scalafix will never support 2.13.7 and we're waiting for 2.13.8 ? |
We could also comment out the test for now and merge as is. |
Agreed. I am commenting them to unblock the release. |
3a0cb72
to
cb79760
Compare
> PrettyTypeSuite: > - Defn.Trait - Functor *** FAILED *** (1 millisecond) > --- obtained > +++ expected > -trait Functor[C[`_`]] > +trait Functor[C[_]]
> --- obtained > +++ expected > - val poc = new PkgObjClass > + val poc: PkgObjClass = new PkgObjClass
Thank you for the release!! :) |
No description provided.