tricky (but probably also low priority?) thing tha...
# development
w
tricky (but probably also low priority?) thing that i expect that you all are not seeing in `guice`:
although a symbol in an unnamed package is not available outside of a package, it is available inside of the unnamed package
a
@witty-crayon-22786 I don’t believe so. I’m seeing cross-package issues
w
the effect of fixing that for this repository though would be a ton of ambiguity (tens of these projects have classes named e.g.
Employee
in the unnamed package)
so… 1) probably not a priority, 2) would require special casing.
a
I’m not certain what you’re talking about?
and they reference other classes in their own unnamed package
a
Oh! You’re talking about the different repo that you’re working on. I get it now.
w
to special case it, we’d have to distinguish “this unnamed package” from “that unnamed package”
…eh. i guess i could still fix it, and then at least folks will get a ton of ambiguity warnings, even without the special casing.
a
the distinction is its source file location, right?
w
the implied compilation unit, yea