Hide top-level package by masking import from _root_

[som-snytt]

import _root_.{jdk => _}

object Test extends App {
  import jdk.CollectionConverters._
  val xs = java.util.List.of(42)
  println(xs.asScala)
}

Currently, we can only mask a root context that is a "predef" object.

It would be nice to also mask an arbitrary package introduced by a root context, such as import _root_.java as _.

It would be even nicer to mask rooted packages from the class path.

Unfortunately, rooted packages are not currently modeled as root contexts per se.

#14781 (comment)

In that sense, there is an impedance mismatch between this syntax and the "mental model" for rooted packages. But it's just syntax.

Also, note that predef is not an import: it competes at level 4 precedence.

I don't know whether users commonly mask predef, where you'd normally ask for -Yno-imports or whatever, but it seems healthy to provide another tool in controlling the "global" namespace, which can be polluted by anything on the class path.

Currently, it's possible to specify a root for hygienic purposes, but not exclude it for convenience.

[som-snytt]

The terminology used here isn't quite coherent. (Top-level packages are not imported and not root-imported. They are available without a prefix.) The underlying issue is that if there is a top-level package on the class path, such as jdk from the JDK, it is preferred to "root imports".

The early ticket was #2856 when the situation was reversed.

[som-snytt]

Probably the solution is "java module support" or equivalent. Instead of excluding a rooted package, you must request access to module packages.