Opaque types are not visible when referenced by package

[scf37]

Compiler version

3.4.0

Minimized code

package foo

opaque type Bar = bar.Bar

object bar:
  class Bar()

  object Bar:
    def apply(): foo.Bar =
      new Bar()

Output

[error] 10 |      new Bar()
[error]    |      ^^^^^^^^^
[error]    |    Found:    foo.bar.Bar
[error]    |    Required: foo.Bar²
[error]    |
[error]    |    where:    Bar  is a class in object bar
[error]    |              Bar² is a type in the top-level definitions in package foo
[error]    |
[error]    | longer explanation available when compiling with `-explain`

Expectation

Successful compilation since bar.Bar.apply is in scope of opaque type foo.Bar

[som-snytt]

Duplicates #19609

I'll leave this open since the other PR is not merged. (So I can't test it to be sure.)

[sjrd]

I don't think this is a duplicate.

This is as designed, AFAICT. The top-level opaque type desugars into being a member of a "package object", as per the spec of top-level definitions. So it is equivalent to

package foo

object FileName$package {
  opaque type Bar = bar.Bar
}

object bar:
  class Bar()

  object Bar:
    def apply(): foo.FileName$package.Bar =
      new Bar()

and now it's clear that Bar.apply is not within the private scope of FileName$package where the opaque type alias would be transparent.

[Gedochao]

Thanks for the clarification @sjrd.
Closing this, as this works as intended.