os-rust/tests/ui/reachable/expr_again.stderr

error: unreachable statement
  --> $DIR/expr_again.rs:8:9
   |
LL |         continue;
   |         -------- any code following this expression is unreachable
LL |         println!("hi");
   |         ^^^^^^^^^^^^^^ unreachable statement
   |
note: the lint level is defined here
  --> $DIR/expr_again.rs:3:9
   |
LL | #![deny(unreachable_code)]
   |         ^^^^^^^^^^^^^^^^
   = note: this error originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to 1 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 09:41:41 -04:00			`error: unreachable statement`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/expr_again.rs:8: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 \| continue;`
			`\| -------- any code following this expression is unreachable`
Update UI tests 2018-02-23 03:42:32 +03:00			`LL \| println!("hi");`
Bless tests 2021-10-14 13:28:28 -05:00			`\| ^^^^^^^^^^^^^^ unreachable statement`
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_again.rs:3: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			`\| ^^^^^^^^^^^^^^^^`
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
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 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 09:41:41 -04:00