os-rust/tests/ui/slightly-nice-generic-literal-messages.rs

use std::marker;

struct Foo<T,U>(T, marker::PhantomData<U>);

fn main() {
    match Foo(1.1, marker::PhantomData) {
        1 => {}
    //~^ ERROR mismatched types
    //~| expected struct `Foo<{float}, _>`
    //~| found type `{integer}`
    //~| expected struct `Foo`, found integer
    }

}
Fallout: tests. As tests frequently elide things, lots of changes here. Some of this may have been poorly rebased, though I tried to be careful and preserve the spirit of the test. 2015-02-12 10:29:52 -05:00			`use std::marker;`

			`struct Foo<T,U>(T, marker::PhantomData<U>);`
rustc: make error messages containing generic more self-explanatory. Unsuffixed literals like 1 and 1.1, and free type parameters sometimes have to be printed in error messages, which ended up with <V0>, <VI0> and <VF0>. This change puts the words "generic" and "integer"/"float" into the message so it's not a completely black box. 2014-01-13 22:08:28 +11:00
			`fn main() {`
Fallout: tests. As tests frequently elide things, lots of changes here. Some of this may have been poorly rebased, though I tried to be careful and preserve the spirit of the test. 2015-02-12 10:29:52 -05:00			`match Foo(1.1, marker::PhantomData) {`
rustc: make error messages containing generic more self-explanatory. Unsuffixed literals like 1 and 1.1, and free type parameters sometimes have to be printed in error messages, which ended up with <V0>, <VI0> and <VF0>. This change puts the words "generic" and "integer"/"float" into the message so it's not a completely black box. 2014-01-13 22:08:28 +11:00			`1 => {}`
Fix testsuite errors 2015-01-12 01:01:44 -05:00			`//~^ ERROR mismatched types`
Specific labels when referring to "expected" and "found" types 2019-11-13 14:16:56 -08:00			//~\| expected struct `Foo<{float}, _>`
Move to {integer} and {float} 2016-07-28 09:49:31 -07:00			//~\| found type `{integer}`
Improve type mismatch error messages Replace "integral variable" with "integer" and replace "floating-point variable" with "floating-point number" to make the message less confusing. 2018-12-31 20:43:08 -05:00			//~\| expected struct `Foo`, found integer
rustc: make error messages containing generic more self-explanatory. Unsuffixed literals like 1 and 1.1, and free type parameters sometimes have to be printed in error messages, which ended up with <V0>, <VI0> and <VF0>. This change puts the words "generic" and "integer"/"float" into the message so it's not a completely black box. 2014-01-13 22:08:28 +11:00			`}`

			`}`