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
mod a {pubstructFoo;implFoo{pubfnbar(){}}}fnmain(){use std::io::File::open;use a::Foo::bar;}
Only the import from non-std module is reported as "error: Cannot import from a trait or type implementation". It is inconsistent and both should be recognized as error.
Some of the rustc internal code actually presume that is the case. Failing to do that leads to bug such as #15528.
The text was updated successfully, but these errors were encountered:
This is probably a general cross-crate vs local crate problem, not specific to std.
edwardw
changed the title
Inconsistent behavior when importing type implementation from std and non-std modules
Inconsistent behavior when importing type implementation from local crate vs. cross-crate
Jul 14, 2014
Consider the following:
Only the import from non-std module is reported as "error: Cannot import from a trait or type implementation". It is inconsistent and both should be recognized as error.
Some of the rustc internal code actually presume that is the case. Failing to do that leads to bug such as #15528.
The text was updated successfully, but these errors were encountered: