rust/tests/ui/suppressed-error.rs

fn main() {
    let (x, y) = ();
//~^ ERROR mismatched types
//~| expected unit type `()`
//~| found tuple `(_, _)`
//~| expected `()`, found
    return x;
}
rustc: Don't call type_error_message() with ty_err as the expected type In #6319, several people mentioned they ran into a "computing fictitious type" ICE in trans. This turns out to be because some of my recent changes to typeck::check::_match resulted in type errors getting reported with ty_err as the expected type, which meant the errors were suppressed, and typechecking incorrectly succeeded (since the errors weren't recorded). Changed the error messages in these cases not to use an expected type at all, rather, printing out a string describing the type that was expected (which is what the code originally did). The result is a bit repetitive and the proliferation of error-reporting functions in typeck::infer is a bit annoying, but I thought it was important to fix this now; more cleanup can happen later. 2013-05-11 17:51:00 -07:00			`fn main() {`
Update tests with the new error messages 2014-10-21 03:40:15 +02:00			`let (x, y) = ();`
Fix testsuite errors 2015-01-12 01:01:44 -05:00			`//~^ ERROR mismatched types`
review comments: tweak prefix strings 2019-11-14 14:08:08 -08:00			//~\| expected unit type `()`
Specific labels when referring to "expected" and "found" types 2019-11-13 14:16:56 -08:00			//~\| found tuple `(_, _)`
Modify primary span label for E0308 The previous output was unintuitive to users. 2023-01-02 18:00:33 -08:00			//~\| expected `()`, found
rustc: Don't call type_error_message() with ty_err as the expected type In #6319, several people mentioned they ran into a "computing fictitious type" ICE in trans. This turns out to be because some of my recent changes to typeck::check::_match resulted in type errors getting reported with ty_err as the expected type, which meant the errors were suppressed, and typechecking incorrectly succeeded (since the errors weren't recorded). Changed the error messages in these cases not to use an expected type at all, rather, printing out a string describing the type that was expected (which is what the code originally did). The result is a bit repetitive and the proliferation of error-reporting functions in typeck::infer is a bit annoying, but I thought it was important to fix this now; more cleanup can happen later. 2013-05-11 17:51:00 -07:00			`return x;`
rustdoc: Change all code-blocks with a script find src -name '.rs' \| xargs sed -i '' 's/~~~.{\.rust}/```rust/g' find src -name '.rs' \| xargs sed -i '' 's/ ~~~$/ ```/g' find src -name '.rs' \| xargs sed -i '' 's/^~~~$/ ```/g' 2013-09-23 17:20:36 -07:00			`}`