-
Notifications
You must be signed in to change notification settings - Fork 226
Issues: bytecodealliance/wasm-tools
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Version where there is "<dash> <only number> <dash>" section cannot be parsed
#1692
opened Jul 20, 2024 by
andrzejressel
added eq, partial_eq traits for many wasmparser types
#1690
opened Jul 18, 2024 by
thesuhas
Loading…
fix(wit-parser): improve checking for stable feature gates
#1689
opened Jul 18, 2024 by
vados-cosmonic
Loading…
wit-parser::decoding::decode
should error when given a core module
#1673
opened Jul 15, 2024 by
rylev
Relicensing
wasm-tools
and this repository's crates
#1637
opened Jun 26, 2024 by
alexcrichton
45 of 47 tasks
shrink: Ineffective on non-tree-like expressions (?)
wasm-mutate
Issues related to the `wasm-mutate` crate
#1633
opened Jun 24, 2024 by
alexcrichton
Enable binary encoding and printing of multi-package wit files
#1609
opened Jun 11, 2024 by
macovedj
Loading…
Check
...BACKTRACE
variables gracefully before running tests
#1578
opened May 26, 2024 by
azaslavsky
•
Draft
wasi-virt throws error in wasm-compose (redirected from wasi-virt to Wasm-tools)
wasm-compose
Issues related to the `wasm-compose` crate
#1565
opened May 17, 2024 by
thesuhas
proposal: wit-parser: create distinct imported and exported TypeDefs, Functions, and Interfaces in a Resolve
#1497
opened Apr 15, 2024 by
ydnar
wasmparser::validator::ComponentState::validate_and_register_named_types
should return Result
instead of bool
#1486
opened Apr 4, 2024 by
rylev
Previous Next
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.