rust/tests/ui/imports/issue-1697.rs

// Testing that we don't fail abnormally after hitting the errors

use unresolved::*; //~ ERROR unresolved import `unresolved` [E0432]
                   //~^ maybe a missing crate `unresolved`?

fn main() {}
test: Add a test for #1697 2012-02-22 23:14:27 -06:00			`// Testing that we don't fail abnormally after hitting the errors`

Point at path segment on module not found Point at the correct path segment on a import statement where a module doesn't exist. New output: ```rust error[E0432]: unresolved import `std::bar` --> <anon>:1:10 \| 1 \| use std::bar::{foo1, foo2}; \| ^^^ Could not find `bar` in `std` ``` instead of: ```rust error[E0432]: unresolved import `std::bar::foo1` --> <anon>:1:16 \| 1 \| use std::bar::{foo1, foo2}; \| ^^^^ Could not find `bar` in `std` error[E0432]: unresolved import `std::bar::foo2` --> <anon>:1:22 \| 1 \| use std::bar::{foo1, foo2}; \| ^^^^ Could not find `bar` in `std` ``` 2017-07-23 17:15:45 -05:00			use unresolved::*; //~ ERROR unresolved import `unresolved` [E0432]
Don't recommend `extern crate` syntax 2019-08-05 09:50:37 -05:00			//~^ maybe a missing crate `unresolved`?
test: Add a test for #1697 2012-02-22 23:14:27 -06:00
rustc: reduce redundant resolve errors. 2014-06-05 16:37:52 -05:00			`fn main() {}`