rust/tests/ui/imports/double-import.rs

// This tests that conflicting imports shows both `use` lines
// when reporting the error.

mod sub1 {
    pub fn foo() {} // implementation 1
}

mod sub2 {
    pub fn foo() {} // implementation 2
}

use sub1::foo;
use sub2::foo; //~ ERROR the name `foo` is defined multiple times

fn main() {}
Fixed some nits 2015-05-01 02:46:15 +00:00			// This tests that conflicting imports shows both `use` lines
			`// when reporting the error.`
First attempt at fixing #20591 This isn't quite right, but it's interesting. 2015-04-25 18:09:41 +00:00
			`mod sub1 {`
Fix fallout in tests 2016-02-22 22:33:38 +00:00			`pub fn foo() {} // implementation 1`
First attempt at fixing #20591 This isn't quite right, but it's interesting. 2015-04-25 18:09:41 +00:00			`}`

			`mod sub2 {`
Fix fallout in tests 2016-02-22 22:33:38 +00:00			`pub fn foo() {} // implementation 2`
First attempt at fixing #20591 This isn't quite right, but it's interesting. 2015-04-25 18:09:41 +00:00			`}`

Remove NOTE/HELP annotations from UI tests 2017-12-10 20:29:24 +00:00			`use sub1::foo;`
Clearer Error Message for Duplicate Definition Clearer use of the error message and span labels to communicate duplicaiton defitions/imports. New error format: ``` error[E0428]: the name `Foo` is defined twice --> example.rs:2:1 \| 1 \| trait Foo { } \| ------------- previous definition of the trait `Foo` here 2 \| struct Foo { } \| ^^^^^^^^^^^^^^ `Foo` redefined here = note: `Foo` must be defined only once in the type namespace of this module error: aborting due to previous error ``` 2017-05-18 03:29:58 +00:00			use sub2::foo; //~ ERROR the name `foo` is defined multiple times
First attempt at fixing #20591 This isn't quite right, but it's interesting. 2015-04-25 18:09:41 +00:00
			`fn main() {}`