You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
or if the opaque type is referenced from inside a top level method, e.g.
opaquetypeFoo=Stringdefbar=valfoo:Foo="abc"
so my assumption is that the problem is caused by the fact that the type gets moved to the synthetic package object but the scopes are compared for opaqueness/transparentness at a later point in the compilation pipeline
this is as specified, Foo is in the scope of the wrapping top-level-definition object for the file, and Bar is in its own top level scope. see the docs
Compiler version
3.4.0-RC1-bin-20230825-2616c8b-NIGHTLY and before
Minimized code
Output
Expectation
This should compile. Because
Bar
is defined in the same scope asFoo
the definition of Foo should be transparent inside the body ofBar
.The text was updated successfully, but these errors were encountered: