Assess `-Xsource:3` using community build #769

SethTisue · 2021-04-26T15:50:52Z

This came up with @smarter at https://gitter.im/typelevel/general?at=6086d87e81866c680c48df4f

I've recently added a bunch of Scala 3 syntax under that flag to allow us to deprecate and potentially repurpose some old syntax without harming cross-compatibility with Scala 2, but this hinges on people actually using that flag so it'd be good to know if there's any issues with it

We should at least try it and see what happens.

SethTisue · 2021-04-30T01:51:54Z

https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/2703/

42 green repos, but also lots of failures, most notably scalatest,kind-projector,utest,shapeless,scalatest-3-0; transitively, those prevent most of the build from running

sampling of failure causes:

scalatest: "method without a parameter list overrides a method with a single empty one"
kind-projector: "Either[Int, _] takes no type parameters, expected: 1", I suppose because it's using the old wildcard syntax
utest: "symbol literal is unsupported; use Symbol("hello") instead"
shapeless: "Malformed literal or standard type 'a"

fixes for these could easily be submitted upstream, and then we could re-run and get more results

this is one of those times where we don't primarily want a community build that rewires all the dependencies; we would primarily want to build each repo separately

it would not be super hard for me (or somebody) to write a script that glues all the proj/*.conf files together in an alternate why where each repo is built in its own space, with check-missing: false so that all dependencies would be retrieved from Maven Central et al. at least, I don't think I would run into a bunch of weird trouble doing that

on the other hand, I don't have any further time for this either this week or next, but I could probably return to it after that

smarter · 2021-04-30T09:40:37Z

fixes for these could easily be submitted upstream

I'll see if I can look into it. I think the compiler could also stop emitting errors on symbol sytnax since it's still supported in Scala 3 under a language feature. But for kind-projector at least, the error likely comes from a test exercising the ? syntax since it's still supported even if it's deprecated, and upstream might not want to get rid of it right now.

on the other hand, I don't have any further time for this either this week or next, but I could probably return to it after that

That would be great! No pressure though :).

This commit lets scalatest compile with the Scala 2.13 flag `-Xsource:3` (but does not enable the flag in the build), this came up in scala/scala-dev#769. The changes needed were: - Add missing parens when overriding `Iterator#next()` - Remove usages of symbol literal syntax - Remove usages of procedure syntax - Fix code that relied on any2stringadd

Scala 3 still supports symbol literals even if they require a language import now (cf scala/scala3#11588), so don't emit an error if we find one under -Xsource:3 as that could unnecessarily impede cross-compilation as discovered in scala/scala-dev#769.

Scala 2.13.6 and 2.12.14 will interpret `?` as a wildcard when using the `-Xsource:3` flag (cf scala/scala#9560)). This means that the old kind-projector syntax will no longer work, so it seems like a good time to remove it. This will also allow us to compile more of the community-build with `-Xsource:3` enabled (cf scala/scala-dev#769). Sincet this is a breaking change, we also bump the version to 0.12.0-SNAPSHOT.

smarter · 2021-04-30T11:18:41Z

This commit lets scalatest compile with the Scala 2.13 flag `-Xsource:3` (but does not enable the flag in the build), this came up in scala/scala-dev#769. The changes needed were: - Add missing parens when overriding `Iterator#next()` - Remove usages of symbol literal syntax - Remove usages of procedure syntax - Fix code that relied on any2stringadd

smarter · 2021-05-23T20:54:37Z

@SethTisue do you think you could try running this again now that all the known issues are fixed?

SethTisue · 2021-05-24T14:33:07Z

@smarter sure, after scala/community-build#1418 lands

SethTisue · 2021-05-26T21:22:42Z

queued: https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/2787/

smarter · 2021-05-27T15:12:47Z

https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/2787/artifact/logs/kind-projector-build.log

[kind-projector] [error] /home/jenkins/workspace/scala-2.13.x-jdk11-integrate-community-build/target-0.9.17/project-builds/kind-projector-b0a85b5f7bb05e14140d78d7b4b2515b9a3ab274/src/test/scala/test.scala:17:7: Either[Int, _] takes no type parameters, expected: 1
[kind-projector] [error]   bar[Either[Int, ?]]
[kind-projector] [error]       ^

Looks like kind-projector isn't up-to-date in the community build since that doesn't match the current sources: https://github.com/typelevel/kind-projector/blob/main/src/test/scala/test.scala#L17

SethTisue · 2021-06-09T05:09:03Z

~~https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/2861/~~
https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/2865/

smarter · 2021-06-15T18:55:30Z

Some observations:

Most failures are due to existing warnings turning into errors
specs2 is failing because it's still using the old ? kind-projector syntax, I'll try to make a PR to fix that.
For some reason, the * - test syntax from utest doesn't work anymore, but it's deprecated anyway.
quicklens fails with seemingly weird errors:

[error] /home/smarter/opt/quicklens/quicklens/src/main/scala-2.13+/com.softwaremill.quicklens/package.scala:125:38: method apply in object LensHelper cannot be accessed as a member of object com.softwaremill.quicklens.package.LensHelper from package object quicklens in package quicklens
[error] error after rewriting to `package`.this.LensHelper.<apply: error>
[error] possible cause: maybe a wrong Dynamic method signature?
[error]   def modifyLens[T]: LensHelper[T] = LensHelper[T]()
[error]                                      ^
[error] /home/smarter/opt/quicklens/quicklens/src/main/scala-2.13+/com.softwaremill.quicklens/package.scala:127:46: method apply in object MultiLensHelper cannot be accessed as a member of object com.softwaremill.quicklens.package.MultiLensHelper from package object quicklens in package quicklens
[error] error after rewriting to `package`.this.MultiLensHelper.<apply: error>
[error] possible cause: maybe a wrong Dynamic method signature?
[error]   def modifyAllLens[T]: MultiLensHelper[T] = MultiLensHelper[T]()
[error]                                              ^
[error] two errors found

Which are actually caused by the private on the definition of LensHelper:

case class LensHelper[T] private () {

which now also implies that the apply method is private. This can be fixed by explicitly declaring these methods as public:

diff --git quicklens/src/main/scala-2.13+/com.softwaremill.quicklens/package.scala quicklens/src/main/scala-2.13+/com.softwaremill.quicklens/package.scala
index 9675d9d..ff647d3 100644
--- quicklens/src/main/scala-2.13+/com.softwaremill.quicklens/package.scala
+++ quicklens/src/main/scala-2.13+/com.softwaremill.quicklens/package.scala
@@ -127,14 +127,19 @@ package object quicklens {
   def modifyAllLens[T]: MultiLensHelper[T] = MultiLensHelper[T]()

   case class LensHelper[T] private () {
-
     def apply[U](path: T => U): PathLazyModify[T, U] = macro QuicklensMacros.modifyLazy_impl[T, U]
   }
+  object LensHelper {
+    def apply[T](): LensHelper[T] = new LensHelper[T]
+  }

   case class MultiLensHelper[T] private () {

     def apply[U](path1: T => U, paths: (T => U)*): PathLazyModify[T, U] = macro QuicklensMacros.modifyLazyAll_impl[T, U]
   }
+  object MultiLensHelper {
+    def apply[T](): MultiLensHelper[T] = new MultiLensHelper[T]
+  }

   case class PathLazyModify[T, U](doModify: (T, U => U) => T) {

So overall this is looking good (except the specs2 and utest failures prevent a lot of projects from compiling).

smarter · 2021-06-15T19:18:02Z

etorreborre/specs2#953

This syntax doesn't compile with `-Xsource:3` and thus prevents us from running utest in the Scala 2 community build with this flag enabled (scala/scala-dev#769).

smarter · 2021-06-15T19:29:26Z

com-lihaoyi/utest#253

This syntax doesn't compile with `-Xsource:3` and thus prevents us from running utest in the Scala 2 community build with this flag enabled (scala/scala-dev#769).

SethTisue · 2021-06-15T19:46:19Z

https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/2881/

SethTisue · 2021-06-16T20:02:52Z

new run with fixes for specs2, fastparse, fastparse-scalameta, scalameta:

https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/2887/

SethTisue · 2021-06-16T20:55:42Z

run 2887 shows: BLOCKING DOWNSTREAM: scalatest-3-0 (62), spray-json (53), wartremover (53), json4s (47), scodec-bits (45), fansi (22), akka-stream (21), acyclic (19), scalatags (11), http4s-parboiled2 (9), spire (7), scalamock (2), hasher (1), lift-json (1), decline (1), mainargs (1), tut (1)

for scalatest-3-0 we could just use a JAR from Maven Central instead

spray-json, wartremover, scodec-bits look to me like they probably just need trivial fixes

json4s situation isn't clear to me at a glance

smarter · 2021-06-16T21:04:45Z

[json4s] [error] def ~>*[B >: A, X2 >: X](f: => Rule[S, S, B => B, X2]) = for (a <- rule; fs <- f*) yield fs.foldLeft[B](a) { (b, f) => f(b) }

That f* is a postfix application of a * operator, which conflicts with the new varargs syntax, looks like this was recently fixed upstream: json4s/json4s@b91c3ff

SethTisue · 2021-07-29T23:58:01Z

@smarter after scala/community-build#1456 is done, doing this sort of experiment will become easier

SethTisue · 2021-08-31T02:32:13Z

after scala/community-build#1456 is done, doing this sort of experiment will become easier

that's done now, so I intend to return to this soon-ish

context: scala/scala-dev#769

SethTisue · 2021-09-13T16:53:36Z

there is a new full run here: https://scala-ci.typesafe.com/view/scala-2.13.x/job/scala-2.13.x-jdk11-integrate-community-build/3190/artifact/report.html (scroll down for links to per-repo failure logs)

181 repos are green, so that's good

these are the failures where -Xsource:3 appears, offhand, to be functioning as intended:

sttp, scodec, scalastyle, scala-collection-laws, play-ws, hasher, grizzled, finagle, breeze:
- method without a parameter list overrides a method with a single empty one
spire, scodec-bits, scalamock, scalafx, parboiled, machinist, http4s-parboiled2:
- unary prefix operator definition with empty parameter list is unsupported
specs2, scribe, scalatags, scalafmt, playframework, mainargs, ammonite, akka-management:
- any2stringadd
zinc, twitter-util, scoverage, scala-java-time, macwire, kafka, jwt-scala, acyclic:
- procedure syntax
tut, spray-json, lagom:
- Methods without a parameter list and by-name params can not be converted to functions as m _
treehugger, lift-json:
- view bounds
slick:
- shadowing a nested class of a parent is unsupported

we would need to dig deeper into the following failures to understand them:

akka-http, alpakka-kafka, http4s, lila-ws, mima, quicklens: error after rewriting [...] possible cause: maybe a wrong Dynamic method signature?
data-class, fansi, pprint, sbt-io: (some kind of * vs ? vs _ stuff)
scalachess: type mismatch (* related?)
pascal: PolyVals.this.Const[A, _] takes no type parameters, expected: 1
scala-supertagged: Type-checking succeeded unexpectedly
scalariform: test failure (perhaps just a too-fragile test?)

smarter · 2021-09-13T18:18:36Z

type mismatch (* related?)

Likely the same as #769 (comment), we should deprecate postfix * by default.

SethTisue · 2021-09-27T21:47:23Z

The easily-nerd-sniped side of my personality wants to investigate the failures, but I think I've concluded that wouldn't be an ideal use of my time.

Overall, the results of this experiment were good. I invite anyone disquieted by any of the failures to investigate and, if appropriate, open specific individual tickets on them in scala/bug.

This syntax doesn't compile with `-Xsource:3` and thus prevents us from running utest in the Scala 2 community build with this flag enabled (scala/scala-dev#769).

SethTisue self-assigned this Apr 26, 2021

This comment has been minimized.

Sign in to view

smarter mentioned this issue Apr 30, 2021

Fix compilation with -Xsource:3 scalatest/scalatest#2020

Merged

smarter mentioned this issue Apr 30, 2021

Don't error (only warn) on symbol literals under -Xsource:3 scala/scala#9602

Merged

smarter mentioned this issue Apr 30, 2021

Remove deprecated ? syntax typelevel/kind-projector#186

Merged

smarter added a commit to smarter/utest that referenced this issue Jun 15, 2021

Remove usage of deprecated * - syntax

5573dc6

This syntax doesn't compile with `-Xsource:3` and thus prevents us from running utest in the Scala 2 community build with this flag enabled (scala/scala-dev#769).

smarter mentioned this issue Jun 15, 2021

Remove usage of deprecated * - syntax com-lihaoyi/utest#253

Merged

SethTisue mentioned this issue Sep 13, 2021

minor code improvement scalameta/scalameta#2472

Merged

SethTisue added a commit to SethTisue/community-build that referenced this issue Sep 13, 2021

make core compile under -Xsource:3

740b62c

context: scala/scala-dev#769

SethTisue mentioned this issue Sep 13, 2021

make core compile under -Xsource:3 scala/community-build#1484

Merged

SethTisue added a commit to SethTisue/community-build that referenced this issue Sep 13, 2021

make core compile under -Xsource:3

cb7a762

context: scala/scala-dev#769

SethTisue added a commit to SethTisue/community-build that referenced this issue Sep 13, 2021

make core compile under -Xsource:3

91935f7

context: scala/scala-dev#769

SethTisue added a commit to scala/community-build that referenced this issue Sep 13, 2021

make core compile under -Xsource:3 (#1484)

be23b46

context: scala/scala-dev#769

SethTisue closed this as completed Sep 27, 2021

som-snytt mentioned this issue Sep 28, 2021

Enable -Xsource:3 and reduce noise lightbend-labs/mima#663

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Assess `-Xsource:3` using community build #769

Assess `-Xsource:3` using community build #769

SethTisue commented Apr 26, 2021

This comment has been minimized.

SethTisue commented Apr 30, 2021 •

edited

smarter commented Apr 30, 2021

smarter commented Apr 30, 2021

smarter commented May 23, 2021

SethTisue commented May 24, 2021

SethTisue commented May 26, 2021

smarter commented May 27, 2021

SethTisue commented Jun 9, 2021 •

edited

smarter commented Jun 15, 2021 •

edited

smarter commented Jun 15, 2021

smarter commented Jun 15, 2021 •

edited

SethTisue commented Jun 15, 2021 •

edited

SethTisue commented Jun 16, 2021

SethTisue commented Jun 16, 2021 •

edited

smarter commented Jun 16, 2021 •

edited

SethTisue commented Jul 29, 2021

SethTisue commented Aug 31, 2021

SethTisue commented Sep 13, 2021 •

edited

smarter commented Sep 13, 2021

SethTisue commented Sep 27, 2021

Assess -Xsource:3 using community build #769

Assess -Xsource:3 using community build #769

Comments

SethTisue commented Apr 26, 2021

This comment has been minimized.

SethTisue commented Apr 30, 2021 • edited

smarter commented Apr 30, 2021

smarter commented Apr 30, 2021

smarter commented May 23, 2021

SethTisue commented May 24, 2021

SethTisue commented May 26, 2021

smarter commented May 27, 2021

SethTisue commented Jun 9, 2021 • edited

smarter commented Jun 15, 2021 • edited

smarter commented Jun 15, 2021

smarter commented Jun 15, 2021 • edited

SethTisue commented Jun 15, 2021 • edited

SethTisue commented Jun 16, 2021

SethTisue commented Jun 16, 2021 • edited

smarter commented Jun 16, 2021 • edited

SethTisue commented Jul 29, 2021

SethTisue commented Aug 31, 2021

SethTisue commented Sep 13, 2021 • edited

smarter commented Sep 13, 2021

SethTisue commented Sep 27, 2021

Assess `-Xsource:3` using community build #769

Assess `-Xsource:3` using community build #769

SethTisue commented Apr 30, 2021 •

edited

SethTisue commented Jun 9, 2021 •

edited

smarter commented Jun 15, 2021 •

edited

smarter commented Jun 15, 2021 •

edited

SethTisue commented Jun 15, 2021 •

edited

SethTisue commented Jun 16, 2021 •

edited

smarter commented Jun 16, 2021 •

edited

SethTisue commented Sep 13, 2021 •

edited