rust/tests/ui/reachable/unreachable-code-ret.stderr

error: unreachable statement
  --> $DIR/unreachable-code-ret.rs:7:5
   |
LL |     return;
   |     ------ any code following this expression is unreachable
LL |     println!("Paul is dead");
   |     ^^^^^^^^^^^^^^^^^^^^^^^^ unreachable statement
   |
note: the lint level is defined here
  --> $DIR/unreachable-code-ret.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 previous error
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`error: unreachable statement`
Renamed ui/dead-code-ret to ui/unreachable-code-ret This test was actually about the unreachable_code flag, not dead_code, so I renamed it for clarity (to prepare for the next commit, where I plan to move a bunch of the dead_code tests to a single folder) 2019-10-24 23:35:17 -05:00			`--> $DIR/unreachable-code-ret.rs:7:5`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Do not trigger unreachable lint in async body and Use span labels 2019-09-21 14:33:02 -05:00			`LL \| return;`
			`\| ------ any code following this expression is unreachable`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`LL \| println!("Paul is dead");`
Bless tests 2021-10-14 13:28:28 -05:00			`\| ^^^^^^^^^^^^^^^^^^^^^^^^ unreachable statement`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Normalise notes with the/is 2020-01-22 17:57:38 -06:00			`note: the lint level is defined here`
Renamed ui/dead-code-ret to ui/unreachable-code-ret This test was actually about the unreachable_code flag, not dead_code, so I renamed it for clarity (to prepare for the next commit, where I plan to move a bunch of the dead_code tests to a single folder) 2019-10-24 23:35:17 -05:00			`--> $DIR/unreachable-code-ret.rs:3:9`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
			`LL \| #![deny(unreachable_code)]`
			`\| ^^^^^^^^^^^^^^^^`
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 13:52:25 -06:00			= note: this error originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
			`error: aborting due to previous error`