rust/tests/ui/reachable/expr_block.stderr

error: unreachable expression
  --> $DIR/expr_block.rs:10:9
   |
LL |         return;
   |         ------ any code following this expression is unreachable
LL |         22
   |         ^^ unreachable expression
   |
note: the lint level is defined here
  --> $DIR/expr_block.rs:4:9
   |
LL | #![deny(unreachable_code)]
   |         ^^^^^^^^^^^^^^^^

error: unreachable statement
  --> $DIR/expr_block.rs:25:9
   |
LL |         return;
   |         ------ any code following this expression is unreachable
LL |         println!("foo");
   |         ^^^^^^^^^^^^^^^ unreachable statement
   |
   = note: this error originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)

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 09:41:41 -04:00			`error: unreachable expression`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/expr_block.rs:10: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 09:41:41 -04:00			`\|`
Do not trigger unreachable lint in async body and Use span labels 2019-09-21 12:33:02 -07:00			`LL \| return;`
			`\| ------ any code following this expression is unreachable`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| 22`
Do not trigger unreachable lint in async body and Use span labels 2019-09-21 12:33:02 -07:00			`\| ^^ unreachable expression`
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 09:41:41 -04:00			`\|`
Normalise notes with the/is 2020-01-22 23:57:38 +00:00			`note: the lint level is defined here`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/expr_block.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 09:41:41 -04:00			`\|`
Update UI tests 2018-02-23 03:42:32 +03: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 09:41:41 -04:00			`\| ^^^^^^^^^^^^^^^^`

			`error: unreachable statement`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/expr_block.rs:25: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 09:41:41 -04:00			`\|`
Do not trigger unreachable lint in async body and Use span labels 2019-09-21 12:33:02 -07:00			`LL \| return;`
			`\| ------ any code following this expression is unreachable`
Update UI tests 2018-02-23 03:42:32 +03:00			`LL \| println!("foo");`
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 18:22:13 -04: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 14:52:25 -05: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 09:41:41 -04:00
Revert "Change error count messages" This reverts commit 5558c64f33446225739c1153b43d2e309bb4f50e. 2017-07-02 13:49:30 +03: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 09:41:41 -04:00