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
Copy file name to clipboardExpand all lines: src/tools/clippy/tests/ui/crashes/ice-6255.stderr
+1-21Lines changed: 1 addition & 21 deletions
Original file line number
Diff line number
Diff line change
@@ -9,25 +9,5 @@ LL | define_other_core!();
9
9
|
10
10
= note: this error originates in the macro `define_other_core` (in Nightly builds, run with -Z macro-backtrace for more info)
11
11
12
-
error[E0659]: `core` is ambiguous
13
-
--> tests/ui/crashes/ice-6255.rs:12:5
14
-
|
15
-
LL | core::panic!();
16
-
| ^^^^ ambiguous name
17
-
|
18
-
= note: ambiguous because of a conflict between a macro-expanded name and a less macro-expanded name from outer scope during import or macro resolution
19
-
= note: `core` could refer to a built-in crate
20
-
note: `core` could also refer to the crate imported here
21
-
--> tests/ui/crashes/ice-6255.rs:6:9
22
-
|
23
-
LL | extern crate std as core;
24
-
| ^^^^^^^^^^^^^^^^^^^^^^^^^
25
-
...
26
-
LL | define_other_core!();
27
-
| -------------------- in this macro invocation
28
-
= help: use `crate::core` to refer to this crate unambiguously
29
-
= note: this error originates in the macro `define_other_core` (in Nightly builds, run with -Z macro-backtrace for more info)
30
-
31
-
error: aborting due to 2 previous errors
12
+
error: aborting due to 1 previous error
32
13
33
-
For more information about this error, try `rustc --explain E0659`.
Copy file name to clipboardExpand all lines: tests/ui/imports/issue-109148.stderr
+1-39Lines changed: 1 addition & 39 deletions
Original file line number
Diff line number
Diff line change
@@ -9,43 +9,5 @@ LL | m!();
9
9
|
10
10
= note: this error originates in the macro `m` (in Nightly builds, run with -Z macro-backtrace for more info)
11
11
12
-
error[E0659]: `std` is ambiguous
13
-
--> $DIR/issue-109148.rs:13:5
14
-
|
15
-
LL | use std::mem;
16
-
| ^^^ ambiguous name
17
-
|
18
-
= note: ambiguous because of a conflict between a macro-expanded name and a less macro-expanded name from outer scope during import or macro resolution
19
-
= note: `std` could refer to a built-in crate
20
-
note: `std` could also refer to the crate imported here
21
-
--> $DIR/issue-109148.rs:6:9
22
-
|
23
-
LL | extern crate core as std;
24
-
| ^^^^^^^^^^^^^^^^^^^^^^^^^
25
-
...
26
-
LL | m!();
27
-
| ---- in this macro invocation
28
-
= help: use `crate::std` to refer to this crate unambiguously
29
-
= note: this error originates in the macro `m` (in Nightly builds, run with -Z macro-backtrace for more info)
30
-
31
-
error[E0659]: `std` is ambiguous
32
-
--> $DIR/issue-109148.rs:14:7
33
-
|
34
-
LL | use ::std::mem as _;
35
-
| ^^^ ambiguous name
36
-
|
37
-
= note: ambiguous because of a conflict between a macro-expanded name and a less macro-expanded name from outer scope during import or macro resolution
38
-
= note: `std` could refer to a built-in crate
39
-
note: `std` could also refer to the crate imported here
40
-
--> $DIR/issue-109148.rs:6:9
41
-
|
42
-
LL | extern crate core as std;
43
-
| ^^^^^^^^^^^^^^^^^^^^^^^^^
44
-
...
45
-
LL | m!();
46
-
| ---- in this macro invocation
47
-
= note: this error originates in the macro `m` (in Nightly builds, run with -Z macro-backtrace for more info)
48
-
49
-
error: aborting due to 3 previous errors
12
+
error: aborting due to 1 previous error
50
13
51
-
For more information about this error, try `rustc --explain E0659`.
= note: ambiguous because of a conflict between a macro-expanded name and a less macro-expanded name from outer scope during import or macro resolution
19
-
= note: `core` could refer to a built-in crate
20
-
note: `core` could also refer to the crate imported here
= note: ambiguous because of a conflict between a macro-expanded name and a less macro-expanded name from outer scope during import or macro resolution
38
-
= note: `core` could refer to a built-in crate
39
-
note: `core` could also refer to the crate imported here
0 commit comments