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
Reported by @xeno-by , the current scheme of inserting a named import and leaving wildcard imports unchanged can produce ambiguous imports, even if named imports have higher precedence
scala>objectX { classC }
defined objectX
scala>objectY { classC }
defined objectY
scala> locally { importX._; importY.C; newC }
res0:Y.C=Y$C@5ac646b3
scala> locally { importY.C; locally { importX._; newC } }
<console>:38:error: reference to C is ambiguous;
it is imported twice in the same scope by
importX._
and importY.C
locally { importY.C; locally { importX._; newC } }
The text was updated successfully, but these errors were encountered:
Reported by @xeno-by , the current scheme of inserting a named import and leaving wildcard imports unchanged can produce ambiguous imports, even if named imports have higher precedence
The text was updated successfully, but these errors were encountered: