WebAssembly / WebAssembly/wabt
Shall the objdump API be included in libwabtjs target
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 8.1k
- Forks
- 827
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 18
Description
currently the target libwabtjs will export APIs:
validate(): void;
resolveNames(): void;
generateNames(): void;
applyNames(): void;
toText(options: ToTextOptions): string;
toBinary(options: ToBinaryOptions): ToBinaryResult;
destroy(): void;
is it possible to export the objdump API for the JS side, so if user want to get the objdump info, they do not need to start up a process?
I suppose the objDump() just return the text will be good, how do you think? Thank you.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names the libwabtjs target and the objdump API; start by tracing how that target exposes its current methods and how objdump is currently invoked. Done means the objdump capability is available from the JavaScript target with a defined result, including whether text output is sufficient.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, javascript, wasm
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100