8 Commits

Author	SHA1	Message	Date
Niko Matsakis	e416518e68	update test cases to reflect new messages	2016-05-02 11:47:10 -04:00
mdinger	7b82a93be3	Fix testsuite errors	2015-01-12 01:34:13 -05:00
Jakub Bukaj	3db13f4892	Always drop var IDs from type variables modulo -Z verbose, per PR discussion	2014-10-29 23:56:22 +01:00
Jakub Bukaj	66fbe4c22c	Update tests with the new diagnostic tweaks	2014-10-29 23:56:22 +01:00
Jakub Bukaj	1484f9cd46	Update tests with the new error messages	2014-10-24 19:43:47 +02:00
Jonas Hietala	9968ae2554	Adjust the error messages to match the pattern "expected foo, found bar" ... Closes #8492	2014-08-24 09:53:01 +02:00
Alex Crichton	3585c64d09	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-25 14:27:42 -07:00
Tim Chevalier	cdb52c0201	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