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

tests/cases/conformance/parser/ecmascript5/parserKeywordsAsIdentifierName2.ts(2,1): error TS2304: Cannot find name 'a'.
tests/cases/conformance/parser/ecmascript5/parserKeywordsAsIdentifierName2.ts(2,12): error TS1010: '*/' expected.


==== tests/cases/conformance/parser/ecmascript5/parserKeywordsAsIdentifierName2.ts (2 errors) ====
    // 'public' should be marked unusable, should complain on trailing /*
    a.public /*
    ~
!!! error TS2304: Cannot find name 'a'.
               
!!! error TS1010: '*/' expected.
Added error 'prologue' to each error baseline. 2014-09-12 22:35:07 +02:00			`tests/cases/conformance/parser/ecmascript5/parserKeywordsAsIdentifierName2.ts(2,1): error TS2304: Cannot find name 'a'.`
Sort diagnostics in our baseline output. This was we don't get noisy baselines just because a different phase of the compiler reported the diagnostic. This helps with Yui's refactoring work to move grammar checks into the type checker. 2014-12-17 00:56:56 +01:00			`tests/cases/conformance/parser/ecmascript5/parserKeywordsAsIdentifierName2.ts(2,12): error TS1010: '*/' expected.`
Added error 'prologue' to each error baseline. 2014-09-12 22:35:07 +02:00

Report error on unclosed multiline comment. Fixes #22 2014-07-15 02:39:20 +02:00			`==== tests/cases/conformance/parser/ecmascript5/parserKeywordsAsIdentifierName2.ts (2 errors) ====`
			`// 'public' should be marked unusable, should complain on trailing /*`
			`a.public /*`
			`~`
Sort diagnostics in our baseline output. This was we don't get noisy baselines just because a different phase of the compiler reported the diagnostic. This helps with Yui's refactoring work to move grammar checks into the type checker. 2014-12-17 00:56:56 +01:00			`!!! error TS2304: Cannot find name 'a'.`

			`!!! error TS1010: '*/' expected.`