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

typeCoercion.js includes BigInt literal without "features: [BigInt]" #1252

Closed
Constellation opened this issue Sep 30, 2017 · 1 comment
Closed

Comments

@Constellation
Copy link
Member

New typeCoercion.js includes BigInt literal like 0n. And it causes some test failures like test262/test/built-ins/String/prototype/indexOf/position-tointeger.js if VM does not support BigInt literal.
But test262/test/built-ins/String/prototype/indexOf/position-tointeger.js is essentially unrelated to BigInt.

Since BigInt is new feature, and since typeCoercion.js is not marked with features: [BigInt], BigInt(0) is better way.

@leobalter
Copy link
Member

Harness files are not required to contain any frontmatter, and for that we don't expect runners to parse harness files for features tags, those should be used on the tests files including them, as the one you mentioned has the features tag for BigInt, already.

The features.yml includes features requirements for includes. Our built-in linter tool will confirm every test including typeCoercion.js has the features BigInt included.

We might need to revisit this, but for now this is the best we have.

leobalter pushed a commit that referenced this issue Oct 3, 2017
typeCoercion.js is included in several tests which are not marked as `features: [BigInt]`.
Since BigInt is new feature, we should not make the above unrelated tests failed due to
lack of BigInt syntax support.

Close #1252.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants