rust/tests/ui/use/use-paths-as-items.rs

// Each path node in a `use` declaration must be treated as an item. If not, the following code
// will trigger an ICE.
//
// Related issue: #25763

use std::{mem, ptr};
use std::mem; //~ ERROR the name `mem` is defined multiple times

fn main() {}
Associate each path in a `use` declaration with the item in the AST map Currently, for `use` declarations with multiple paths, only the `use` item itself is saved in the AST map, not the individual path nodes. This can lead to a problem when a span of a specific path node is needed. For example, #24818 caused an ICE because of this, in `ImportResolver::check_for_conflicting_import()`. Fixes #25763. 2015-05-26 02:27:15 +00:00			// Each path node in a `use` declaration must be treated as an item. If not, the following code
			`// will trigger an ICE.`
			`//`
			`// Related issue: #25763`

			`use std::{mem, ptr};`
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 std::mem; //~ ERROR the name `mem` is defined multiple times
Associate each path in a `use` declaration with the item in the AST map Currently, for `use` declarations with multiple paths, only the `use` item itself is saved in the AST map, not the individual path nodes. This can lead to a problem when a span of a specific path node is needed. For example, #24818 caused an ICE because of this, in `ImportResolver::check_for_conflicting_import()`. Fixes #25763. 2015-05-26 02:27:15 +00:00
			`fn main() {}`