@lrytz @SethTisue I'm not sure distinguishing "warning 3" from "behavior 3" is the right direction. That is because of Lukas's recent remark, and also the ticket about case class apply access. I saw an early comment from Seth about "the behavior change is only under -Xsource:3", so I think "behind a flag" meant "anything goes".

In the new regime, there is regular 2.13 which has some deprecations, -Xsource:3 which makes them cat=Scala3Migration (error by default) and also progresses more warnings, then -Xsource:3-X (or any version > 3.0.0) which adds behavior changes such as previously witnessed only in moody teenagers.

Changes are more-or-less listed under -Xsource:help (yay).

To me this looks good. Thank you for all the attention to detail, and for the help text! @SethTisue wdyt?

I had forgotten that this proceeded. I see the point here was to split migration help over the two settings.

There's a different branch issue/12883-xsource-ergo to improve ergonomics but maybe that stalled when switching version setting to a Choice enumeration. That was September. trial/library-xsource3 was June.

I see that even if a deprecation is issued at 2.13, at 3 a (possibly more menacing) warning is issued as Scala3Migration, and 3-X may implement the new behavior.

The possible exception to this rule is "benign syntax", such as accepting import p.*, which is not benign if you're trying to import that identifier. So the lines to be drawn here might be fine (i.e. debatable).

Edit: ...and the warning issued at 3 is configured at error, so -Xmigration is the quickie way to detune to warning only. IIRC.

Somewhat optimistically, I'll try to audit that the 4 config are reflected in tests: 2.13., 3+migration, 3, 3-X. The code switches between 2, 3, 3-X.

It's not reasonable to warn about how parser constructs interpolations, unless it emits a warning that is only summarized: at the end, it could say you used string interpolation, which has new semantics etc; assuming it's too much work to check for shadowing StringContext; or refcheck that interpolations only use scala.StringContext, including extension methods.

@lrytz thanks for not asking me to revisit this PR. Your clever use of attachments cleans up nicely.

Thanks for the improved mnemonic for -Xsource:3-X, "cross-building" instead of merely "extended".

I see you quashed a couple of messages under X, thanks. I would need to run under a debugger to see the change for any2stringadd. Does that defer the deprecation?

"cross building" is when you get mad at sbt.

... the change for any2stringadd. Does that defer the deprecation?

any2stringadd is annotated @deprecated, so you get an ordinary deprecation with source:2.13 and now also source:3. The compiler hack is now under source:3-X, it hides the symbol from implicit search. It's debatable whether that's actually useful, as it doesn't change any behavior (it only disables it). Cross-building projects anyway use the dotty compiler to figure out what doesn't work in Scala 3.

maybe -Xsource:cross as the name?

@SethTisue it's actually any version string that compares greater than "3.0.0", which includes "3-X" where the X is anything like FINAL or SNAPSHOT, etc. I liked that it was not a magic string.

(Entrance to warren: I think 3-SNAPSHOT compares wrong, but didn't pursue the cottontail.)

I liked that it was not a magic string

The advantage of a magic string is that it gives something a fixed name so we — and not just we, but the whole community — can refer to it conversation, documentation, PR review, blog posts, etc. I think it should have one name. (And I think we can find a better one than 3-X, which I find cryptic.)

-Xsource:3-X starts and ends in -X, it's a mnemonic!

Since I never get what I love, you or Lukas at your behest may invent something, or invent a version string that always compares last, namely, future for -Xsource:future.

Now that I said it, I also love that idea. Then we can also say the tag line, "-Xsource: Back to the future!"

I see from a glance at the source that none sorts higher than any version, so -Xsource:none should already work. The mnemonic is that there is no future in Scala 2.

@SethTisue this is ready for review

I guess you can click on it, too. The first weird error:

[info] Running 152 / 152 (100.00%) scripted tests with RunFromSourceMain
[info] Running apiinfo/circular-structure
[info] Running source-dependencies/malformed-class-name
[info] Running apiinfo/java-basic
[info] Running source-dependencies/malformed-class-name-with-dollar
[info] Running apiinfo/main-discovery
[info] Running source-dependencies/mixed-java-invalidations
[info] Running apiinfo/source-path
[info] [info] welcome to sbt 1.9.7 (Oracle Corporation Java 1.8.0_332)
[info] [info] loading project definition from /tmp/sbt_499533b0/project
[info] [info] compiling 1 Scala source to /tmp/sbt_499533b0/project/target/scala-2.12/sbt-1.0/classes ...
[info] [info] done compiling
[info] [info] set current project to sbt_499533b0 (in build file:/tmp/sbt_499533b0/)
[info] [success] Total time: 0 s, completed Jan 18, 2024 10:18:01 AM
[info] [info] welcome to sbt 1.9.7 (Oracle Corporation Java 1.8.0_332)
[info] [info] loading project definition from /tmp/sbt_499533b0/project
[info] [info] loading settings for project sbt_499533b0 from common.sbt ...
[info] [info] set current project to sbt_499533b0 (in build file:/tmp/sbt_499533b0/)
[info] [info] compiling 2 Scala sources and 1 Java source to /tmp/sbt_499533b0/target/classes ...
[info] [error] ## Exception when compiling 3 sources to /tmp/sbt_499533b0/target/classes
[info] [error] java.util.ServiceConfigurationError: xsbti.compile.CompilerInterface2: jar:file:/home/jenkins/.ivy2/local/org.scala-lang/scala2-sbt-bridge/2.13.13-bin-SNAPSHOT/jars/scala2-sbt-bridge.jar!/META-INF/services/xsbti.compile.CompilerInterface2:1: Illegal provider-class name: 6scala.tools.xsbt.CompilerBridge
[info] [error] java.util.ServiceLoader.fail(ServiceLoader.java:239)

edit: scrolling right

Illegal provider-class name: 6scala.tools.xsbt.CompilerBridge

If this were merged at Thanksgiving, it wouldn't have weird build errors after MLK, Jr Day. (U.S. reference points.)

lrytz just re-rebases on top, but I am way too lazy slash process-averse to do that.

My main concern here is the naming. (Which I did ponder repeatedly during my long silence... sorry about that...)

I do want:

• fixed names so everyone can consistently refer to it in documentation, chat rooms, etc

I don't want:

• multiple ways of the saying the same thing (e.g. -Xsource:3 and -Xsource:3migrate)
• magic behavior around sort order of option names
  • (that's not there anymore, is it?)
• new naming formats if we can avoid them (I can't think of anything we already have resembling the mashed-together "3migrate" and "3cross")

I suggest we keep -Xsource:3 and let it continue to have its current meaning, and I think we should not add the -Xsource:3migrate alias.

So then this PR would simply add -Xsource:cross with the new behavior. I don't think the "3" in the name is necessary.

@som-snytt @lrytz wdyt?

-Xsource:help is awesome, thanks for that.

Any label is OK by me.

Dotty has -source:3.0-migration which is "more forgiving", so if anything I would suggest -Xsource:3-migration for warning and -Xsource:3 for behavior ("actually setting the source version, whatever that entails").

However, 3 and cross would be just as distinctive and effective.

"Gee that's a dumb name for an option" does not impede the dotty team. Nor should it us.

Let's see what Lukas thinks.

The vibe I'm going for here is "There's -Xsource:3, you already know what that does, it still does that. We also added a new thing you might want instead." Instead of a "we changed everything around" vibe.

We did change everything around. There used to be a mix of warnings and behavior changes until Lukas imposed Swiss tidiness.

The user complaint was "don't warn about the behavior change I asked for", so -Xsource:3 used to mean behavior. My fault for not adopting the dotty model, but I think I assumed that option would always maximize whatever was "backported" from dotty. That broke down when "downwards" implicit search was split out.

But whatever option names are chosen now is OK, people will figure it out.

We did change everything around

Okay, I see what you mean. Yes, I acknowledge that I'm idealizing the coherence of the prior state a bit :-)

The most common use case for -Xsource is likely migration to a new version, so -Xsource:3 and -Xsource:3cross sounds good. I'm in favor of keeping the 3, it adds useful information for build file readers - is 3-cross better?

It seems Scala 2 is anyway different from dotty

• If youre on 3.x, then 3.x-migration dials back some hard errors (and enables -rewrite)
• future enables deprecation warnings, future-migration is for -rewrite of those

I don't know if -Xsource:3.x[-migration] are intended to be used if you're on 3.(x-n) or on 3.(x+n).

I'd be okay with -Xsource:3-cross. They are using hyphens in the Scala 3 names at https://docs.scala-lang.org/scala3/reference/language-versions/source-compatibility.html

It seems Scala 2 is anyway different from dotty

(I just suggested at https://users.scala-lang.org/t/scala-3-porting-experiences/9753/5 that perhaps Scala 3 ought to also offer a flag specifically for crossbuilt projects, since 3.4 will now warn by default about tons of stuff that isn't actionable in crossbuilt projects.)

🎉

Anyone else notice that the original -Xsource:3-X is the same as -Xsource:3-cross?

@som-snytt @lrytz I just did an edit pass over the PR description — y'all might want to take another look as well.

I see that -Xsource:3-migration doesn't mean anything. Only -Xsource:3-cross is a specially labeled version. (In the normal universe, 3-foo sorts higher than 3.0.0, so that was the reason or mnemonic for it to mean "drop migration semantics, we're way beyond that".)

The help text mentions scala3-migration is the "warning category" for -Xsource:3, but it's not in the comment here; also how to detune it so you can limp along with mere warnings.

Edit: added a few words above. Now, I would like to go grocery shopping, please, so that I can squeeze in some exercise after.