WebAssembly / WebAssembly/binaryen

Commandline tools and missing -o

Open
#7,408 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
WebAssembly
Stars
8.6k
Forks
885
Avg merge
1d 19h
Merged PRs (30d)
69

Description

wasm-opt warns on not having an output file. That make sense as it avoids a common error, but also it is not an error itself as there are valid use cases for wasm-opt without writing output (wasm-opt --metrics for example).

Other tools atm neither warn nor error, but we should probably do one of the two.

Contributor guide

Open the contributing guide

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.

Research direction

Start at the command-line entry points for wasm-opt and the other tools, comparing how they handle a missing output file. Review the --metrics use case and existing warning or error behavior. Done means the tools follow a documented, consistent policy without rejecting valid no-output commands.

Written by the indexing model from the issue text.

Assessment

Tech stack
wasm
Domain
cli, compilers
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.