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
One of the big arguments in favor of RFC #390 (enum namespacing) was that it was easy to get the old behavior back using an import. There is one case, however, where this is not possible: an enum defined in an unnameable scope. I think the only place in current Rust where one can do this is inside a function.
mod a {fnb(){enumFoo{Bar}useFoo::Bar;// Tries to find to Foo in the crate scope (or as an external crate).useself::Foo::Bar;// Tries to find a::Foo.}}
I haven't come up with a good syntax to propose for this operation, though.
The text was updated successfully, but these errors were encountered:
One of the big arguments in favor of RFC #390 (enum namespacing) was that it was easy to get the old behavior back using an import. There is one case, however, where this is not possible: an enum defined in an unnameable scope. I think the only place in current Rust where one can do this is inside a function.
I haven't come up with a good syntax to propose for this operation, though.
The text was updated successfully, but these errors were encountered: