Skip to content
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

Merged
merged 3 commits into from Nov 12, 2021
Merged

support scala 2.13.7 #1493

merged 3 commits into from Nov 12, 2021

Conversation

bjaglin
Copy link
Collaborator

@bjaglin bjaglin commented Nov 2, 2021

No description provided.

@@ -1,5 +1,5 @@
rules = [
ExplicitResultTypes,
# ExplicitResultTypes,
Copy link
Collaborator Author

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.

Copy link
Collaborator

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!

@mlachkar
Copy link
Collaborator

mlachkar commented Nov 2, 2021

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!

@bjaglin
Copy link
Collaborator Author

bjaglin commented Nov 3, 2021

There are 2 tests failing, that were not failing with the Scalameta 4.4.29 update, and look related to compiler changes.

1/

###########> Diff       <###########

=======
=> Diff
=======
--- obtained
+++ expected
@@ -194,3 +194,3 @@
∙
-    val poc = new PkgObjClass
+    val poc: PkgObjClass = new PkgObjClass
   }
         
[info] - test/explicitResultTypes/BetterRscCompat.scala *** FAILED *** (592 milliseconds)

That seems related to https://github.com/scalameta/scalameta/pull/2502/files#diff-65b44c93ebcf284cd66432972b21ee5671b9ea3c1de809c400f7c8bc16b8041fR109-R115

2/

[info] PrettyTypeSuite:
[info] - Defn.Trait - Functor *** FAILED *** (1 millisecond)
[info]   --- obtained
[info]   +++ expected
[info]   
[info]   ===========
[info]   => Obtained
[info]   ===========
[info]   trait Functor[C[`_`]]
[info]            
[info]   =======
[info]   => Diff
[info]   =======
[info]   --- obtained
[info]   +++ expected
[info]   @@ -1,1 +1,1 @@
[info]   -trait Functor[C[`_`]]
[info]   +trait Functor[C[_]] (PrettyTypeSuite.scala:58)

Not sure about this one... Any insight @tgodzik?

@SethTisue
Copy link
Contributor

SethTisue commented Nov 3, 2021

Not sure about this one...

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

@som-snytt
Copy link

class C[_] is disallowed, not trait F[C[_]].

@tgodzik
Copy link
Contributor

tgodzik commented Nov 3, 2021

Not sure about this one... Any insight @tgodzik?

Looks like _ is now treated as a name instead of a wildcard. Not sure where it stems from, but I could try to investigate next week. Is writing Functor[C[]] needed currently though? I don't think we would every write [] for the explicit results types?

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.

@som-snytt
Copy link

som-snytt commented Nov 3, 2021

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.

@tOverney
Copy link

Does this bug means that scalafix will never support 2.13.7 and we're waiting for 2.13.8 ?

@tgodzik
Copy link
Contributor

tgodzik commented Nov 12, 2021

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.

@bjaglin
Copy link
Collaborator Author

bjaglin commented Nov 12, 2021

We could also comment out the test for now and merge as is.

Agreed. I am commenting them to unblock the release.

@bjaglin bjaglin marked this pull request as ready for review November 12, 2021 17:17
> 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
@tOverney
Copy link

Thank you for the release!! :)

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.

None yet

6 participants