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

[bigint] ToNumeric type coercion tests via "-UnaryExpression" #1243

Closed
wants to merge 4 commits into from

Conversation

thejoshwolfe
Copy link
Contributor

With the BigInt spec changes, unary minus uses ToNumeric instead of just ToNumber. This test uses a unary minus expression to test the type coercion corner cases for ToNumeric.

This PR is based on #1241. Not sure I did all the paperwork properly to indicate and facilitate that.

Josh Wolfe added 4 commits September 25, 2017 15:26
* Number.prototype.toString() has a lot of implementation-specified
  behavior, which means we shouldn't test something like
  (123.456).toString().
* Fix copypaste error
* ToBigInt error tests should also test ToPrimitive errors.
@rwaldron rwaldron changed the title [bigint] ToNumeric type coercion tests via uniary minus [bigint] ToNumeric type coercion tests via -UnaryExpression Sep 26, 2017
@rwaldron rwaldron changed the title [bigint] ToNumeric type coercion tests via -UnaryExpression [bigint] ToNumeric type coercion tests via "-UnaryExpression" Sep 26, 2017
@thejoshwolfe
Copy link
Contributor Author

Following up from the review feedback in #1241, this PR needs to take a different approach. I'll open a new PR for this issue.

@thejoshwolfe thejoshwolfe deleted the tonumeric branch October 11, 2017 14:10
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

Successfully merging this pull request may close these issues.

1 participant