4 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
Nick Cameron	45fd7cd359	Enable a test for .. in range patterns.	2014-10-02 17:35:20 +13:00
Alex Crichton	d3e171861f	Test fixes from the rollup	2014-09-29 10:13:31 -07:00
Nick Cameron	2c589df6a2	Test for .. in range patterns	2014-09-29 11:45:20 +13:00