TypeScript/tests/baselines/reference/evalAfter0.types
Wesley Wigham 5353475fce Always collect type and symbol baselines (#18621)
* Always generate type & symbol baselines

* Accept changed shadowed baselines

* Accept brand new type and symbol baselines

* Allow `getTypeAtLocation` to return undefined in the type writer

* Accept baselines which had missing type information

* Bind container for dynamically names enum members so they may be printed

* Accept type/symbol baselines for enums with computed members

* First pass at reducing typeWriter memory overhead

* Use generators to allow for type and symbol baselines with no cache

* Accept new baselines for tests whose output was fixed by better newline splitting

* Hard cap on number of declarations printed, cache declaration print text

* handle differing newlines better still to handle RWC newlines

* Lower abridging count, accept abridged baselines

* Limit max RWC error output size, limit RWC type and symbol baseline input size

* Move skip logic into type and symbol baseliner to streamline error handling

* Accept removal of empty baselines

* Canonicalize path earlier to handle odd paths in input files

* Do canonicalization earlier still, also ensure parallel perf profiles for different targets do not trample one another

* No need to pathify again
2017-09-22 15:52:04 -07:00

21 lines
450 B
Plaintext

=== tests/cases/compiler/evalAfter0.ts ===
(0,eval)("10"); // fine: special case for eval
>(0,eval)("10") : any
>(0,eval) : (x: string) => any
>0,eval : (x: string) => any
>0 : 0
>eval : (x: string) => any
>"10" : "10"
declare var eva;
>eva : any
(0,eva)("10"); // error: no side effect left of comma (suspect of missing method name or something)
>(0,eva)("10") : any
>(0,eva) : any
>0,eva : any
>0 : 0
>eva : any
>"10" : "10"