wasm/web: direct table calls in wasm_runtime.js skip __padBigintArgs

Open Beginner friendly
#15,140 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust, wasm
Domain
backend

Research direction

Start in crates/perry-codegen-wasm/src/wasm_runtime.js and review the direct fn(...) calls into the WASM function table, comparing them with the paths fixed in #15108 and #15110. Route remaining calls through __padBigintArgs; done when direct table calls pad arguments consistently and no longer trigger the reported BigInt type error for callees with higher declared arity.

Written by the indexing model from the issue text.

Description

area:compiler effort:S impact:low platform:wasm type:bug

Some direct fn(...) calls into the WASM function table in crates/perry-codegen-wasm/src/wasm_runtime.js pass their arguments without __padBigintArgs, unlike the paths #15108 and #15110 fixed. A callee whose declared arity exceeds the passed arguments then receives non-BigInt padding and can hit Cannot mix BigInt and other types. Audit the remaining direct table calls and route them through the shared padding helper.

Raised by CodeRabbit on #15108; pre-existing. Not the same as #15104, which is about __padBigintArgs itself reading a program-patched Math.max. Related: #15137.

Dominant language
Rust
Stars
4.9k
Forks
166
Avg merge
6h 5m
Merged PRs (30d)
949

Getting set up

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 PerryTS/perry

All issues in PerryTS/perry

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.