maxmustermann/TypeScript
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
TypeScript/tests/baselines/reference/parserMemberAccessExpression1.errors.txt

38 lines
1.9 KiB
Plaintext
Raw Normal View History

Added error 'prologue' to each error baseline.
2014-09-12 22:35:07 +02:00
tests/cases/conformance/parser/ecmascript5/Generics/parserMemberAccessExpression1.ts(1,1): error TS2304: Cannot find name 'Foo'.
tests/cases/conformance/parser/ecmascript5/Generics/parserMemberAccessExpression1.ts(2,1): error TS2304: Cannot find name 'Foo'.
tests/cases/conformance/parser/ecmascript5/Generics/parserMemberAccessExpression1.ts(3,1): 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
tests/cases/conformance/parser/ecmascript5/Generics/parserMemberAccessExpression1.ts(3,7): error TS1005: '(' expected.
Improve the flexibility of speculative parsing. We now no longer fail a speculative parse just because an error was encountered at any point while speculating. instead, we allow the speculative function that is being called to determine if the parse was successful or not. Only if it decides it was not successful is parsing rewound. This improves our error recovery in several cases (esp. around arrow functions). it will also help in a followup refactoring to prevent lookahead/speculative parsing from causing lambda allocations.
2014-12-04 17:53:45 +01:00
tests/cases/conformance/parser/ecmascript5/Generics/parserMemberAccessExpression1.ts(3,8): 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
tests/cases/conformance/parser/ecmascript5/Generics/parserMemberAccessExpression1.ts(3,13): error TS1005: ')' expected.
Added error 'prologue' to each error baseline.
2014-09-12 22:35:07 +02:00
tests/cases/conformance/parser/ecmascript5/Generics/parserMemberAccessExpression1.ts(4,1): 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
tests/cases/conformance/parser/ecmascript5/Generics/parserMemberAccessExpression1.ts(4,7): error TS1005: '(' expected.
Improve the flexibility of speculative parsing. We now no longer fail a speculative parse just because an error was encountered at any point while speculating. instead, we allow the speculative function that is being called to determine if the parse was successful or not. Only if it decides it was not successful is parsing rewound. This improves our error recovery in several cases (esp. around arrow functions). it will also help in a followup refactoring to prevent lookahead/speculative parsing from causing lambda allocations.
2014-12-04 17:53:45 +01:00
tests/cases/conformance/parser/ecmascript5/Generics/parserMemberAccessExpression1.ts(4,8): 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
tests/cases/conformance/parser/ecmascript5/Generics/parserMemberAccessExpression1.ts(4,16): error TS1005: ')' expected.
Added error 'prologue' to each error baseline.
2014-09-12 22:35:07 +02:00
Improve the flexibility of speculative parsing. We now no longer fail a speculative parse just because an error was encountered at any point while speculating. instead, we allow the speculative function that is being called to determine if the parse was successful or not. Only if it decides it was not successful is parsing rewound. This improves our error recovery in several cases (esp. around arrow functions). it will also help in a followup refactoring to prevent lookahead/speculative parsing from causing lambda allocations.
2014-12-04 17:53:45 +01:00
==== tests/cases/conformance/parser/ecmascript5/Generics/parserMemberAccessExpression1.ts (10 errors) ====
Add snapshot of compiler sources
2014-07-13 01:04:16 +02:00
Foo<T>();
~~~
Harness now prints category and code when running tests.
2014-09-12 00:19:57 +02:00
!!! error TS2304: Cannot find name 'Foo'.
Add snapshot of compiler sources
2014-07-13 01:04:16 +02:00
Foo.Bar<T>();
~~~
Harness now prints category and code when running tests.
2014-09-12 00:19:57 +02:00
!!! error TS2304: Cannot find name 'Foo'.
Add snapshot of compiler sources
2014-07-13 01:04:16 +02:00
Foo<T>.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 TS2304: Cannot find name 'Foo'.
Add snapshot of compiler sources
2014-07-13 01:04:16 +02:00
~
Improve the flexibility of speculative parsing. We now no longer fail a speculative parse just because an error was encountered at any point while speculating. instead, we allow the speculative function that is being called to determine if the parse was successful or not. Only if it decides it was not successful is parsing rewound. This improves our error recovery in several cases (esp. around arrow functions). it will also help in a followup refactoring to prevent lookahead/speculative parsing from causing lambda allocations.
2014-12-04 17:53:45 +01:00
!!! 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
~~~
!!! error TS2304: Cannot find name 'Bar'.
Improve the flexibility of speculative parsing. We now no longer fail a speculative parse just because an error was encountered at any point while speculating. instead, we allow the speculative function that is being called to determine if the parse was successful or not. Only if it decides it was not successful is parsing rewound. This improves our error recovery in several cases (esp. around arrow functions). it will also help in a followup refactoring to prevent lookahead/speculative parsing from causing lambda allocations.
2014-12-04 17:53:45 +01:00
~
!!! 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
Foo<T>.Bar<T>();
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 'Foo'.
Add snapshot of compiler sources
2014-07-13 01:04:16 +02:00
~
Improve the flexibility of speculative parsing. We now no longer fail a speculative parse just because an error was encountered at any point while speculating. instead, we allow the speculative function that is being called to determine if the parse was successful or not. Only if it decides it was not successful is parsing rewound. This improves our error recovery in several cases (esp. around arrow functions). it will also help in a followup refactoring to prevent lookahead/speculative parsing from causing lambda allocations.
2014-12-04 17:53:45 +01:00
!!! error TS1005: '(' expected.
~~~
!!! 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
Reference in a new issue Copy permalink