Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

stack size mismatch error messages are unclear

Open
#1,675 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

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
wasm
Domain
compilers

Research direction

No file or test is named in the issue. Start by searching the specification repository for the two quoted error messages and inspect the stack-mismatch and implicit-return paths; done means these cases clearly report stack underflow or excess entries, with the relevant test suite updated and passing.

Written by the indexing model from the issue text.

Description

"error: type mismatch in <thing>, expected [<thing>] but got []" and "error: type mismatch in implicit return, expected [] but got [<thing>]" dont make it clear that the stack has underflowed/too many entries

i would very much appreciate if these messages were "error: stack underflows at <thing>" and "error: stack too big on implicit return (x entries too many/few)" instead for these cases

Dominant language
WebAssembly
Stars
3.5k
Forks
540
Avg merge
11h 12m
Merged PRs (30d)
11

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 WebAssembly/spec

All issues in WebAssembly/spec

Similar issues

More Compilers issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.