TypeScript/tests/baselines/reference/parserErrantEqualsGreaterThanAfterFunction1.errors.txt

tests/cases/conformance/parser/ecmascript5/ErrorRecovery/parserErrantEqualsGreaterThanAfterFunction1.ts(1,14): error TS1144: '{' or ';' expected.


==== tests/cases/conformance/parser/ecmascript5/ErrorRecovery/parserErrantEqualsGreaterThanAfterFunction1.ts (1 errors) ====
    function f() => 4;
                 ~~
!!! error TS1144: '{' or ';' expected.
Don't report an error directly when parsing a function body. 2014-12-01 09:31:31 +01:00			`tests/cases/conformance/parser/ecmascript5/ErrorRecovery/parserErrantEqualsGreaterThanAfterFunction1.ts(1,14): error TS1144: '{' or ';' expected.`
Added error 'prologue' to each error baseline. 2014-09-12 22:35:07 +02:00

Support modifiers on object literal methods and accessors, and question tokens on object literal methods. This makes parsing of these constructs the same whether they are in an object literal or a class. This is important for incrementla parsing for knowing if we can reuse these nodes if we run into them. 2014-12-11 07:30:40 +01:00			`==== tests/cases/conformance/parser/ecmascript5/ErrorRecovery/parserErrantEqualsGreaterThanAfterFunction1.ts (1 errors) ====`
Add snapshot of compiler sources 2014-07-13 01:04:16 +02:00			`function f() => 4;`
			`~~`
Support modifiers on object literal methods and accessors, and question tokens on object literal methods. This makes parsing of these constructs the same whether they are in an object literal or a class. This is important for incrementla parsing for knowing if we can reuse these nodes if we run into them. 2014-12-11 07:30:40 +01:00			`!!! error TS1144: '{' or ';' expected.`