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.

Sign up for GitHub

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

Jump to bottom

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

Closed
wants to merge 4 commits into from
Closed

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

wants to merge 4 commits into from

Commits on Sep 25, 2017

  1. don't test non-trivial number toString() 

    * 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.
    Josh Wolfe committed Sep 25, 2017
    Configuration menu
    Copy the full SHA
    47e35f5 View commit details
    Browse the repository at this point in the history

  2. no sense in testing if BigInt is defined when 0n syntax is used elsew… 

    …here in the same file
    Josh Wolfe committed Sep 25, 2017
    Configuration menu
    Copy the full SHA
    5405d37 View commit details
    Browse the repository at this point in the history

  3. add ToBoolean support to typeCoercion.js

    Josh Wolfe committed Sep 25, 2017
    Configuration menu
    Copy the full SHA
    46fba43 View commit details
    Browse the repository at this point in the history

Commits on Sep 26, 2017

  1. ToNumeric type coercion tests via uniary minus

    Josh Wolfe committed Sep 26, 2017
    Configuration menu
    Copy the full SHA
    b4a93c7 View commit details
    Browse the repository at this point in the history