5 Commits

Author	SHA1	Message	Date
Esteban Küber	78ae8feebb	Improve wording and spans for unexpected token ... * Point at where the token was expected instead of the last token successfuly parsed. * Only show `unexpected token` if the next char and the unexpected token don't have the same span. * Change some cfail and pfail tests to ui test. * Don't show all possible tokens in span label if they are more than 6.	2017-03-25 15:36:59 -07:00
Esteban Küber	03eca71381	Point at last valid token on failed expect_one_of ... ```rust error: expected one of `.`, `;`, `?`, `}`, or an operator, found `)` --> $DIR/token-error-correct-3.rs:29:9 | 25 | foo() | - expected one of `.`, `;`, `?`, `}`, or an operator after this ... 29 | } else { | ^ unexpected token ```	2017-03-24 23:37:25 -07:00
Vadim Petrochenkov	2092682191	resolve: Do not use "resolve"/"resolution" in error messages	2017-01-12 10:08:27 +03:00
Vadim Petrochenkov	09aba18e10	More systematic error reporting in path resolution	2016-12-26 15:01:49 +03:00
Vadim Petrochenkov	3fb676afb0	Move some compile-fail tests into UI directory	2016-12-26 12:58:33 +03:00