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

tests/cases/conformance/parser/ecmascript5/SkippedTokens/parserSkippedTokens16.ts(1,1): error TS2304: Cannot find name 'foo'.
tests/cases/conformance/parser/ecmascript5/SkippedTokens/parserSkippedTokens16.ts(1,6): error TS1005: ';' expected.
tests/cases/conformance/parser/ecmascript5/SkippedTokens/parserSkippedTokens16.ts(1,8): error TS2304: Cannot find name 'Bar'.
tests/cases/conformance/parser/ecmascript5/SkippedTokens/parserSkippedTokens16.ts(1,12): error TS1005: ';' expected.
tests/cases/conformance/parser/ecmascript5/SkippedTokens/parserSkippedTokens16.ts(2,22): error TS1127: Invalid character.
tests/cases/conformance/parser/ecmascript5/SkippedTokens/parserSkippedTokens16.ts(3,3): error TS1109: Expression expected.
tests/cases/conformance/parser/ecmascript5/SkippedTokens/parserSkippedTokens16.ts(6,5): error TS1138: Parameter declaration expected.
tests/cases/conformance/parser/ecmascript5/SkippedTokens/parserSkippedTokens16.ts(8,14): error TS1109: Expression expected.


==== tests/cases/conformance/parser/ecmascript5/SkippedTokens/parserSkippedTokens16.ts (8 errors) ====
    foo(): Bar { }
    ~~~
!!! error TS2304: Cannot find name 'foo'.
         ~
!!! error TS1005: ';' expected.
           ~~~
!!! error TS2304: Cannot find name 'Bar'.
               ~
!!! error TS1005: ';' expected.
    function Foo      () #   { }
                         
!!! error TS1127: Invalid character.
    4+:5
      ~
!!! error TS1109: Expression expected.
    module M {
    function a(
        : T) { }
        ~
!!! error TS1138: Parameter declaration expected.
    }
    var x       =
                 
!!! error TS1109: Expression expected.
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/SkippedTokens/parserSkippedTokens16.ts(1,1): error TS2304: Cannot find name 'foo'.`
Added error 'prologue' to each error baseline. 2014-09-12 22:35:07 +02:00			`tests/cases/conformance/parser/ecmascript5/SkippedTokens/parserSkippedTokens16.ts(1,6): error TS1005: ';' expected.`
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/SkippedTokens/parserSkippedTokens16.ts(1,8): error TS2304: Cannot find name 'Bar'.`
Added error 'prologue' to each error baseline. 2014-09-12 22:35:07 +02:00			`tests/cases/conformance/parser/ecmascript5/SkippedTokens/parserSkippedTokens16.ts(1,12): error TS1005: ';' expected.`
			`tests/cases/conformance/parser/ecmascript5/SkippedTokens/parserSkippedTokens16.ts(2,22): error TS1127: Invalid character.`
			`tests/cases/conformance/parser/ecmascript5/SkippedTokens/parserSkippedTokens16.ts(3,3): error TS1109: Expression expected.`
			`tests/cases/conformance/parser/ecmascript5/SkippedTokens/parserSkippedTokens16.ts(6,5): error TS1138: Parameter declaration expected.`
			`tests/cases/conformance/parser/ecmascript5/SkippedTokens/parserSkippedTokens16.ts(8,14): error TS1109: Expression expected.`


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/SkippedTokens/parserSkippedTokens16.ts (8 errors) ====`
Add snapshot of compiler sources 2014-07-13 01:04:16 +02:00			`foo(): Bar { }`
			`~~~`
Harness now prints category and code when running tests. 2014-09-12 00:19:57 +02:00			`!!! error TS2304: Cannot find name 'foo'.`
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 TS1005: ';' expected.`
Add snapshot of compiler sources 2014-07-13 01:04:16 +02:00			`~~~`
Harness now prints category and code when running tests. 2014-09-12 00:19:57 +02:00			`!!! error TS2304: Cannot find name 'Bar'.`
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 TS1005: ';' expected.`
Add snapshot of compiler sources 2014-07-13 01:04:16 +02:00			`function Foo () # { }`

Harness now prints category and code when running tests. 2014-09-12 00:19:57 +02:00			`!!! error TS1127: Invalid character.`
Add snapshot of compiler sources 2014-07-13 01:04:16 +02:00			`4+:5`
			`~`
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			`module M {`
			`function a(`
			`: T) { }`
			`~`
Harness now prints category and code when running tests. 2014-09-12 00:19:57 +02:00			`!!! error TS1138: Parameter declaration expected.`
Add snapshot of compiler sources 2014-07-13 01:04:16 +02:00			`}`
			`var x =`

Harness now prints category and code when running tests. 2014-09-12 00:19:57 +02:00			`!!! error TS1109: Expression expected.`