10 Commits

Author	SHA1	Message	Date
P1start	108bca53f0	Make the parser’s ‘expected <foo>, found <bar>’ errors more accurate ... As an example of what this changes, the following code: let x: [int ..4]; Currently spits out ‘expected `]`, found `..`’. However, a comma would also be valid there, as would a number of other tokens. This change adjusts the parser to produce more accurate errors, so that that example now produces ‘expected one of `(`, `+`, `,`, `::`, or `]`, found `..`’.	2014-12-04 13:47:35 +13: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
Patrick Walton	9143688197	librustc: Replace impl Type : Trait with impl Trait for Type. rs=implflipping	2013-02-14 14:44:12 -08:00
Graydon Hoare	d1affff623	Reliciense makefiles and testsuite. Yup.	2012-12-10 17:32:58 -08:00
Tim Chevalier	d4cc7db138	Un-xfail working test	2012-11-15 18:41:17 -08:00
Lindsey Kuper	5a63b2100e	More consistent use of backticks and "expected" in error messages. ... Got some of the debug messages, here, too. I figure it doesn't hurt to get used to doing this even in places where users won't ever see it.	2012-07-13 15:31:39 -07:00
Gareth Daniel Smith	6d86969260	change the test suite //! kind syntax to //~ kind in order to avoid a ... conflict with the new single-line-sugared-inner-doc-comment (`//! ...`).	2012-06-30 12:23:59 +01:00
Niko Matsakis	8a9df5aa38	make it illegal to implicitly capture mutable variables ... this is the final part of #1273	2012-05-07 13:22:42 -07:00
Niko Matsakis	cfa09d35a3	Revert "allow fn exprs to omit arg types" ... This reverts commit 1ba4ca4c4a.	2012-05-03 14:42:34 -07:00
Niko Matsakis	1ba4ca4c4a	allow fn exprs to omit arg types ... also, avoid using type variables for fn args with omitted types unless necessary. This will be important for bound regions in fn types. fixes #2093	2012-05-03 14:32:32 -07:00