rust/tests/ui/reachable/expr_method.stderr

error: unreachable expression
  --> $DIR/expr_method.rs:16:21
   |
LL |     Foo.foo(return, 22);
   |             ------  ^^ unreachable expression
   |             |
   |             any code following this expression is unreachable
   |
note: the lint level is defined here
  --> $DIR/expr_method.rs:5:9
   |
LL | #![deny(unreachable_code)]
   |         ^^^^^^^^^^^^^^^^

error: unreachable call
  --> $DIR/expr_method.rs:21:9
   |
LL |     Foo.bar(return);
   |         ^^^ ------ any code following this expression is unreachable
   |         |
   |         unreachable call

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`
Revert "Remove `#![feature(never_type)]` from tests." This reverts commit 8f6197f39f7d468dfc5b2bd41dae4769992a2f83. 2019-12-11 08:51:28 -06:00			`--> $DIR/expr_method.rs:16:21`
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 \| Foo.foo(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`
Revert "Remove `#![feature(never_type)]` from tests." This reverts commit 8f6197f39f7d468dfc5b2bd41dae4769992a2f83. 2019-12-11 08:51:28 -06:00			`--> $DIR/expr_method.rs:5: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			`\| ^^^^^^^^^^^^^^^^`

Reduce span to function name in unreachable calls 2019-09-06 11:16:11 -05:00			`error: unreachable call`
Revert "Remove `#![feature(never_type)]` from tests." This reverts commit 8f6197f39f7d468dfc5b2bd41dae4769992a2f83. 2019-12-11 08:51:28 -06:00			`--> $DIR/expr_method.rs:21: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 tests 2019-03-09 06:03:44 -06:00			`LL \| Foo.bar(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 call`
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