mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
9ad1e7c46c
rust/src/test/ui/reachable/expr_if.stderr

36 lines
900 B
Plaintext
Raw Normal View History

Various test changes
2019-03-18 22:47:07 -05:00
error: unreachable block in `if` expression
--> $DIR/expr_if.rs:7:17
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
|
Various test changes
2019-03-18 22:47:07 -05:00
LL | if {return} {
| _________________^
LL | | println!("Hello, world!");
LL | | }
| |_____^
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
|
note: lint level defined here
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/expr_if.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
| ^^^^^^^^^^^^^^^^
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
note: any code following this expression is unreachable
--> $DIR/expr_if.rs:7:9
|
LL | if {return} {
| ^^^^^^
Various test changes
2019-03-18 22:47:07 -05:00
error: unreachable statement
--> $DIR/expr_if.rs:27:5
|
LL | println!("But I am.");
| ^^^^^^^^^^^^^^^^^^^^^^
|
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
note: any code following this expression is unreachable
--> $DIR/expr_if.rs:21:9
|
LL | return;
| ^^^^^^
mention nightly in -Z external-macro-backtrace note
2017-11-21 13:48:35 -06:00
= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-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
Various test changes
2019-03-18 22:47:07 -05:00
error: aborting due to 2 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