Don't suggest to use things which weren't found either.

[leoschwarz]

Sometimes it is very useful when rustc figures out that the faulty module use you just made is probably just a typo and directs you a potential match (thanks for that!). However it also directs you to potential matches which haven't been found either in certain cases, for example compiling

use DoesntExist1;
use DoesntExist2;

currently (2016-11-28) yields with both stable and nightly the following output:

error[E0432]: unresolved import `DoesntExist1`
 --> src/lib.rs:1:5
  |
1 | use DoesntExist1;
  |     ^^^^^^^^^^^^ no `DoesntExist1` in the root

error[E0432]: unresolved import `DoesntExist2`
 --> src/lib.rs:2:5
  |
2 | use DoesntExist2;
  |     ^^^^^^^^^^^^ no `DoesntExist2` in the root. Did you mean to use `DoesntExist1`?

While this is merely a suggestion displayed and shouldn't cause any harm at all maybe it might still be worth to check if what is suggested was actually found in the current scope. Or would that be too expensive (e.g. overhead in tracking what was already successfully imported and what not) and is thus left as is by design?

[cyplo]

Is this easy to fix ? If so - maybe worth marking as so and mentioning on Rust Weekly ?

[jseyfried]

@cyplo Yeah, I believe this can be fixed by replacing these lines with _ => None,.

[ioctaptceb]

I think I can take this, if it hasn't been worked on so far!

[tshepang]

@ioctaptceb go for it

[ioctaptceb]

How can I assign myself?

[cyplo]

Not sure if you can via github, due to permissions, but you can just start working on it :) There's a trace in the comments, anyone looking for more work would see them hopefully here in this issue.