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
{{ message }}
Repository navigation
Can't bring nested mod into scope with use foo::foo #5130
Should the use item just be illegal if it collides with an existing name? This issue confused me for quite a while with the rust-sdl package's sdl crate that contains an sdl mod.
This is an "expected no-shadowing, got shadowing" case. it now rejects at parse level because the use things must come first. (This is actually the case that rule was introduced to handle).
Activity
catamorphism commentedon Apr 25, 2013
Seems non-critical for 0.7. Nominating for milestone #1 (well-defined).
graydon commentedon May 2, 2013
This is an "expected no-shadowing, got shadowing" case. it now rejects at parse level because the
usethings must come first. (This is actually the case that rule was introduced to handle).Auto merge of rust-lang#5130 - JohnTitor:split-up-index-slice, r=flip…