`parseInt(x, undefined)` and `parseInt(x, null)` should be treated as if they were `parseInt(x, 10)`

Open
#99 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, rust
Domain
compilers

Research direction

Start by running /test262/test/built-ins/parseInt/S15.1.2.2_A3.1_T3.js and inspect the failure in the Rust JavaScript implementation. Trace how parseInt receives undefined and null for its radix; done means the test passes and both cases behave like radix 10.

Written by the indexing model from the issue text.

Description

This causes /test262/test/built-ins/parseInt/S15.1.2.2_A3.1_T3.js to fail.

Dominant language
Rust
Stars
54
Forks
2
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from y21/dash

All issues in y21/dash

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.