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

error: unreachable statement
  --> $DIR/expr_while.rs:18:9
   |
LL |         println!("Hello, world!");
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
note: lint level defined here
  --> $DIR/expr_while.rs:14:9
   |
LL | #![deny(unreachable_code)]
   |         ^^^^^^^^^^^^^^^^
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

error: unreachable statement
  --> $DIR/expr_while.rs:33:9
   |
LL |         println!("I am dead.");
   |         ^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

error: unreachable statement
  --> $DIR/expr_while.rs:36:5
   |
LL |     println!("I am, too.");
   |     ^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

error: aborting due to 3 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 statement`
stabilise feature(never_type) Replace feature(never_type) with feature(exhaustive_patterns). feature(exhaustive_patterns) only covers the pattern-exhaustives checks that used to be covered by feature(never_type) 2018-01-21 02:44:41 -06:00			`--> $DIR/expr_while.rs:18: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 \| println!("Hello, world!");`
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`
			`--> $DIR/expr_while.rs:14:9`
			`\|`
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			`\| ^^^^^^^^^^^^^^^^`
mention nightly in -Z external-macro-backtrace note 2017-11-21 13:48:35 -06:00			`= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-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 08:41:41 -05:00
			`error: unreachable statement`
Match errors using the callsite of macro expansions 2018-07-19 07:15:43 -05:00			`--> $DIR/expr_while.rs:33: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 \| println!("I am dead.");`
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			`\| ^^^^^^^^^^^^^^^^^^^^^^^`
			`\|`
mention nightly in -Z external-macro-backtrace note 2017-11-21 13:48:35 -06:00			`= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-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 08:41:41 -05:00
			`error: unreachable statement`
Match errors using the callsite of macro expansions 2018-07-19 07:15:43 -05:00			`--> $DIR/expr_while.rs:36:5`
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 \| println!("I am, too.");`
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			`\| ^^^^^^^^^^^^^^^^^^^^^^^`
			`\|`
mention nightly in -Z external-macro-backtrace note 2017-11-21 13:48:35 -06:00			`= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-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 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 3 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