Constructor proxies break when "random" classes pop up on class path

[som-snytt]

Compiler version

3.6.4

Minimized code

class Compiler(c: Int)

@main def test = println:
  Compiler(42)

Output

➜  snips scala-cli compile --server=false -S 3.7.0-RC1 --jvm 17 no-compiler.scala

-- [E177] Reference Error: /home/amarki/snips/no-compiler.scala:5:2 ------------
5 |  Compiler(42)
  |  ^^^^^^^^
  |  Reference to constructor proxy for class Compiler
  |  shadows outer reference to object Compiler in package java.lang
  |
  |  The instance needs to be created with an explicit `new`.
  |
  | longer explanation available when compiling with `-explain`
1 error found
Compilation failed

Expectation

The API was deleted in modern JVMs, so this particular issue is resolved. However, we needn't be exposed to such brittleness.

-Yimports is too blunt an instrument.

It doesn't matter if I

import java.lang.{Compiler as _, *}

which is one of those clever Scala things which may or may not work. Maybe it would work for a Predef.

Maybe a directive could be used to unimport or shadow or otherwise specify a "profile" to compile against.

Noticed IRL at #17563 (comment)

[Gedochao]

The API was deleted in modern JVMs, so this particular issue is resolved.

This note is important, as it compiles fine on JVM > 17.

scala-cli compile repro.scala --jvm 18         
# Compiling project (Scala 3.6.3, JVM (18))
# Compiled project (Scala 3.6.3, JVM (18))

[som-snytt]

Related to #17675 (was #17674)

Besides --release, there is no mechanism for hiding "API" in which we have no interest. The linked discussion is about how imports change meaning.

This ticket is about how a language feature suddenly "stops working". That is why I lodged it as a bug.

I adjusted the priority because it is a small nuisance, and maybe a head-scratcher, but not an impedance.