Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compiler options have different effects on command line vs in fourslash test #25081

Closed
ghost opened this issue Jun 19, 2018 · 1 comment
Closed
Labels
Infrastructure Issue relates to TypeScript team infrastructure

Comments

@ghost
Copy link

ghost commented Jun 19, 2018

TypeScript Version: Version 3.0.0-dev.20180616

Code

/// <reference path="fourslash.ts" />

// @target: esnext

////Symbol.iterator;

verify.noErrors();

This fourslash test fails. But putting Symbol.iterator; in a file and running tsc a.ts --target esnext compiles with no error. // @lib: esnext doesn't work either, even though tsc a.ts --lib esnext works.

@ghost ghost added Bug A bug in TypeScript Infrastructure Issue relates to TypeScript team infrastructure labels Jun 19, 2018
@ghost
Copy link
Author

ghost commented Jun 19, 2018

@rbuckton This works for other options, it probably has something to do with #23893.

This isn't actually about compiler flags, the following compiles fine with no compile flags but fails as a fourslash test:

/// <reference lib="es2015" />
Symbol.iterator;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Infrastructure Issue relates to TypeScript team infrastructure
Projects
None yet
Development

No branches or pull requests

3 participants