rust/tests/ui/reachable/expr_array.stderr

error: unreachable expression
  --> $DIR/expr_array.rs:9:34
   |
LL |     let x: [usize; 2] = [return, 22];
   |                          ------  ^^ unreachable expression
   |                          |
   |                          any code following this expression is unreachable
   |
note: the lint level is defined here
  --> $DIR/expr_array.rs:4:9
   |
LL | #![deny(unreachable_code)]
   |         ^^^^^^^^^^^^^^^^

error: unreachable expression
  --> $DIR/expr_array.rs:14:25
   |
LL |     let x: [usize; 2] = [22, return];
   |                         ^^^^^------^
   |                         |    |
   |                         |    any code following this expression is unreachable
   |                         unreachable expression

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			`error: unreachable expression`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/expr_array.rs:9:34`
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: [usize; 2] = [return, 22];`
Do not trigger unreachable lint in async body and Use span labels 2019-09-21 14:33:02 -05:00			`\| ------ ^^ unreachable expression`
			`\| \|`
			`\| any code following this expression is unreachable`
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_array.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			`\| ^^^^^^^^^^^^^^^^`

			`error: unreachable expression`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/expr_array.rs:14:25`
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: [usize; 2] = [22, return];`
Do not trigger unreachable lint in async body and Use span labels 2019-09-21 14:33:02 -05:00			`\| ^^^^^------^`
			`\| \| \|`
			`\| \| any code following this expression is unreachable`
			`\| 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 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 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