4698b366c4
When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error.
33 lines
1,018 B
Text
33 lines
1,018 B
Text
error: adding items after statements is confusing, since items exist from the start of the scope
|
|
--> $DIR/item_after_statement.rs:12:5
|
|
|
|
|
LL | / fn foo() {
|
|
LL | | println!("foo");
|
|
LL | | }
|
|
| |_____^
|
|
|
|
|
= note: `-D clippy::items-after-statements` implied by `-D warnings`
|
|
|
|
error: adding items after statements is confusing, since items exist from the start of the scope
|
|
--> $DIR/item_after_statement.rs:19:5
|
|
|
|
|
LL | / fn foo() {
|
|
LL | | println!("foo");
|
|
LL | | }
|
|
| |_____^
|
|
|
|
error: adding items after statements is confusing, since items exist from the start of the scope
|
|
--> $DIR/item_after_statement.rs:32:13
|
|
|
|
|
LL | / fn say_something() {
|
|
LL | | println!("something");
|
|
LL | | }
|
|
| |_____________^
|
|
...
|
|
LL | b!();
|
|
| ----- in this macro invocation
|
|
|
|
|
= note: this error originates in the macro `b` (in Nightly builds, run with -Z macro-backtrace for more info)
|
|
|
|
error: aborting due to 3 previous errors
|
|
|