Scala 3 migration warning for implicits found in package prefix

[lrytz]

The implicit scope in Scala 3 no longer includes the requested type's package prefix.

Includes commits of #10573.

Fixes scala/bug#12919

[lrytz]

Seems to be green.

A question is: if an implicit is available both by an import as well as through a prefix of the requested type, is the imported one preferred by spec, by implementation, or just by luck? It seems to be the case in the test as we're not seeing the warning once the import is added, but I haven't checked why.

[som-snytt]

Sorry if I don't understand the question, but implicits in lexical scope are checked before implicit scope. The package prefix was a "part" of the type that contributes to implicit scope.

[som-snytt]

You make it look easy.

[som-snytt]

Just yesterday I was saying, Didn't they undeprecate package object inheritance?

[lrytz]

It's in https://github.com/scala/scala/pull/10573/commits

[SethTisue]

community build regressions here; see scala/community-build#1710 (comment)

[SethTisue]

followup PR is #10685

[xuwei-k]

• unusual error message package object implicits bug#12967