rust/src/test/ui/issue-33525.stderr

error[E0425]: cannot find value `a` in this scope
  --> $DIR/issue-33525.rs:12:5
   |
LL |     a; //~ ERROR cannot find value `a`
   |     ^ not found in this scope

error[E0609]: no field `lorem` on type `&'static str`
  --> $DIR/issue-33525.rs:13:8
   |
LL |     "".lorem; //~ ERROR no field
   |        ^^^^^

error[E0609]: no field `ipsum` on type `&'static str`
  --> $DIR/issue-33525.rs:14:8
   |
LL |     "".ipsum; //~ ERROR no field
   |        ^^^^^

error: aborting due to 3 previous errors

You've got a few errors: E0425, E0609
If you want more information on an error, try using "rustc --explain E0425"
report the total number of errors on compilation failure Prior to this PR, when we aborted because a "critical pass" failed, we displayed the number of errors from that critical pass. While that's the number of errors that caused compilation to abort in that place, that's not what people really want to know. Instead, always report the total number of errors, and don't bother to track the number of errors from the last pass that failed. This changes the compiler driver API to handle errors more smoothly, and therefore is a compiler-api-[breaking-change]. Fixes #42793. 2017-07-02 13:09:09 +00:00			error[E0425]: cannot find value `a` in this scope
			`--> $DIR/issue-33525.rs:12:5`
			`\|`
Update UI tests 2018-02-23 00:42:32 +00:00			LL \| a; //~ ERROR cannot find value `a`
report the total number of errors on compilation failure Prior to this PR, when we aborted because a "critical pass" failed, we displayed the number of errors from that critical pass. While that's the number of errors that caused compilation to abort in that place, that's not what people really want to know. Instead, always report the total number of errors, and don't bother to track the number of errors from the last pass that failed. This changes the compiler driver API to handle errors more smoothly, and therefore is a compiler-api-[breaking-change]. Fixes #42793. 2017-07-02 13:09:09 +00:00			`\| ^ not found in this scope`

			error[E0609]: no field `lorem` on type `&'static str`
			`--> $DIR/issue-33525.rs:13:8`
			`\|`
Update UI tests 2018-02-23 00:42:32 +00:00			`LL \| "".lorem; //~ ERROR no field`
report the total number of errors on compilation failure Prior to this PR, when we aborted because a "critical pass" failed, we displayed the number of errors from that critical pass. While that's the number of errors that caused compilation to abort in that place, that's not what people really want to know. Instead, always report the total number of errors, and don't bother to track the number of errors from the last pass that failed. This changes the compiler driver API to handle errors more smoothly, and therefore is a compiler-api-[breaking-change]. Fixes #42793. 2017-07-02 13:09:09 +00:00			`\| ^^^^^`

			error[E0609]: no field `ipsum` on type `&'static str`
			`--> $DIR/issue-33525.rs:14:8`
			`\|`
Update UI tests 2018-02-23 00:42:32 +00:00			`LL \| "".ipsum; //~ ERROR no field`
report the total number of errors on compilation failure Prior to this PR, when we aborted because a "critical pass" failed, we displayed the number of errors from that critical pass. While that's the number of errors that caused compilation to abort in that place, that's not what people really want to know. Instead, always report the total number of errors, and don't bother to track the number of errors from the last pass that failed. This changes the compiler driver API to handle errors more smoothly, and therefore is a compiler-api-[breaking-change]. Fixes #42793. 2017-07-02 13:09:09 +00:00			`\| ^^^^^`

			`error: aborting due to 3 previous errors`

Update ui tests 2018-02-19 20:40:25 +00:00			`You've got a few errors: E0425, E0609`
			`If you want more information on an error, try using "rustc --explain E0425"`