rust/src/test/ui/reachable/expr_cast.stderr

error: unreachable expression
  --> $DIR/expr_cast.rs:9:13
   |
LL |     let x = {return} as !;
   |             ^^^^^^^^^^^^^
   |
note: lint level defined here
  --> $DIR/expr_cast.rs:4:9
   |
LL | #![deny(unreachable_code)]
   |         ^^^^^^^^^^^^^^^^
note: any code following this expression is unreachable
  --> $DIR/expr_cast.rs:9:14
   |
LL |     let x = {return} as !;
   |              ^^^^^^

error: aborting due to previous error
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 expression`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/expr_cast.rs:9:13`
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 tests 2019-03-09 06:03:44 -06:00			`LL \| let x = {return} as !;`
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_cast.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_cast.rs:9:14`
			`\|`
			`LL \| let x = {return} as !;`
			`\| ^^^^^^`
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 previous error`
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