mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
4d55affc12
rust/tests/ui/reachable/expr_loop.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

38 lines
1.3 KiB
Plaintext
Raw Normal View History

cherry-pick over the tests I wrote for the reachability code For the most part, the current code performs similarly, although it differs in some particulars. I'll be nice to have these tests for judging future changes, as well.
2017-03-21 08:41:41 -05:00
error: unreachable statement
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/expr_loop.rs:8:5
cherry-pick over the tests I wrote for the reachability code For the most part, the current code performs similarly, although it differs in some particulars. I'll be nice to have these tests for judging future changes, as well.
2017-03-21 08:41:41 -05:00
|
Do not trigger unreachable lint in async body and Use span labels
2019-09-21 14:33:02 -05:00
LL | loop { return; }
| ------ any code following this expression is unreachable
Update UI tests
2018-02-22 18:42:32 -06:00
LL | println!("I am dead.");
Bless tests
2021-10-14 13:28:28 -05:00
| ^^^^^^^^^^^^^^^^^^^^^^ unreachable statement
cherry-pick over the tests I wrote for the reachability code For the most part, the current code performs similarly, although it differs in some particulars. I'll be nice to have these tests for judging future changes, as well.
2017-03-21 08:41:41 -05:00
|
Normalise notes with the/is
2020-01-22 17:57:38 -06:00
note: the lint level is defined here
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/expr_loop.rs:4:9
cherry-pick over the tests I wrote for the reachability code For the most part, the current code performs similarly, although it differs in some particulars. I'll be nice to have these tests for judging future changes, as well.
2017-03-21 08:41:41 -05:00
|
Update UI tests
2018-02-22 18:42:32 -06:00
LL | #![deny(unreachable_code)]
cherry-pick over the tests I wrote for the reachability code For the most part, the current code performs similarly, although it differs in some particulars. I'll be nice to have these tests for judging future changes, as well.
2017-03-21 08:41:41 -05:00
| ^^^^^^^^^^^^^^^^
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error.
2021-02-13 13:52:25 -06:00
= note: this error originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)
cherry-pick over the tests I wrote for the reachability code For the most part, the current code performs similarly, although it differs in some particulars. I'll be nice to have these tests for judging future changes, as well.
2017-03-21 08:41:41 -05:00
error: unreachable statement
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/expr_loop.rs:21:5
cherry-pick over the tests I wrote for the reachability code For the most part, the current code performs similarly, although it differs in some particulars. I'll be nice to have these tests for judging future changes, as well.
2017-03-21 08:41:41 -05:00
|
Do not trigger unreachable lint in async body and Use span labels
2019-09-21 14:33:02 -05:00
LL | loop { return; }
| ------ any code following this expression is unreachable
Update UI tests
2018-02-22 18:42:32 -06:00
LL | println!("I am dead.");
Bless tests
2021-10-14 13:28:28 -05:00
| ^^^^^^^^^^^^^^^^^^^^^^ unreachable statement
Point at original span when emitting unreachable lint Fixes #64590 When we emit an 'unreachable' lint, we now add a note pointing at the expression that actually causes the code to be unreachable (e.g. `return`, `break`, `panic`). This is especially useful when macros are involved, since a diverging expression might be hidden inside of a macro invocation.
2019-09-18 17:22:13 -05:00
|
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error.
2021-02-13 13:52:25 -06:00
= note: this error originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)
cherry-pick over the tests I wrote for the reachability code For the most part, the current code performs similarly, although it differs in some particulars. I'll be nice to have these tests for judging future changes, as well.
2017-03-21 08:41:41 -05:00
error: unreachable statement
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/expr_loop.rs:32:5
cherry-pick over the tests I wrote for the reachability code For the most part, the current code performs similarly, although it differs in some particulars. I'll be nice to have these tests for judging future changes, as well.
2017-03-21 08:41:41 -05:00
|
Do not trigger unreachable lint in async body and Use span labels
2019-09-21 14:33:02 -05:00
LL | loop { 'middle: loop { loop { break 'middle; } } }
| -------------------------------------------------- any code following this expression is unreachable
Update UI tests
2018-02-22 18:42:32 -06:00
LL | println!("I am dead.");
Bless tests
2021-10-14 13:28:28 -05:00
| ^^^^^^^^^^^^^^^^^^^^^^ unreachable statement
cherry-pick over the tests I wrote for the reachability code For the most part, the current code performs similarly, although it differs in some particulars. I'll be nice to have these tests for judging future changes, as well.
2017-03-21 08:41:41 -05:00
|
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error.
2021-02-13 13:52:25 -06:00
= note: this error originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)
cherry-pick over the tests I wrote for the reachability code For the most part, the current code performs similarly, although it differs in some particulars. I'll be nice to have these tests for judging future changes, as well.
2017-03-21 08:41:41 -05:00
Revert "Change error count messages" This reverts commit 5558c64f33446225739c1153b43d2e309bb4f50e.
2017-07-02 05:49:30 -05:00
error: aborting due to 3 previous errors
cherry-pick over the tests I wrote for the reachability code For the most part, the current code performs similarly, although it differs in some particulars. I'll be nice to have these tests for judging future changes, as well.
2017-03-21 08:41:41 -05:00
Reference in New Issue Copy Permalink