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

tests/cases/conformance/parser/ecmascript5/ErrorRecovery/parserEmptyParenthesizedExpression1.ts(2,5): error TS1109: Expression expected.


==== tests/cases/conformance/parser/ecmascript5/ErrorRecovery/parserEmptyParenthesizedExpression1.ts (1 errors) ====
    function getObj() {
       ().toString();
        ~
!!! error TS1109: Expression expected.
    }
Added error 'prologue' to each error baseline. 2014-09-12 22:35:07 +02:00			`tests/cases/conformance/parser/ecmascript5/ErrorRecovery/parserEmptyParenthesizedExpression1.ts(2,5): error TS1109: Expression expected.`


Improved lookahead for arrow functions. Fixes issue #34. Specifically: * We no longer automatically assume "()" is a function expression. It must be followed by an arrow, colon, or curly brace. * If an arrow is missing following a signature, but a curly brace is present, we assume the user forgot the arrow and try to parse the body anyway. 2014-07-23 01:47:09 +02:00			`==== tests/cases/conformance/parser/ecmascript5/ErrorRecovery/parserEmptyParenthesizedExpression1.ts (1 errors) ====`
Add snapshot of compiler sources 2014-07-13 01:04:16 +02:00			`function getObj() {`
			`().toString();`
Improved lookahead for arrow functions. Fixes issue #34. Specifically: * We no longer automatically assume "()" is a function expression. It must be followed by an arrow, colon, or curly brace. * If an arrow is missing following a signature, but a curly brace is present, we assume the user forgot the arrow and try to parse the body anyway. 2014-07-23 01:47:09 +02:00			`~`
Harness now prints category and code when running tests. 2014-09-12 00:19:57 +02:00			`!!! error TS1109: Expression expected.`
Add snapshot of compiler sources 2014-07-13 01:04:16 +02:00			`}`