Skip to content

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.

Sign up for GitHub

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

85 Open 265 Closed
85 Open 265 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

wasmparser: Should we put 128-bit SIMD behind a crate feature?
#1899 opened Nov 9, 2024 by Robbepop
1
8
merging wit is not commutative
#1897 opened Nov 7, 2024 by karthik2804
Should hash maps be removed from wasmparser?
#1876 opened Oct 22, 2024 by alexcrichton
Release notes for this repository
#1826 opened Sep 25, 2024 by alexcrichton
wit: unexpected error when referencing the package itself in exports
#1809 opened Sep 19, 2024 by Mossaka
wit: propose to propogate World's name to inline Interfaces' names
#1805 opened Sep 19, 2024 by Mossaka
9
wasmparser: Performance regressions since v0.100.2
#1701 opened Jul 26, 2024 by Robbepop
1
22
wit-component should accept modules with shared memories
#1674 opened Jul 15, 2024 by whitequark
7
wasmparser accepts some malformed modules
#1671 opened Jul 14, 2024 by keithw
5
shrink: Ineffective on non-tree-like expressions (?) wasm-mutate Issues related to the `wasm-mutate` crate
#1633 opened Jun 24, 2024 by alexcrichton
wave: Require escaping some "problematic" unicode characters
#1629 opened Jun 21, 2024 by lann
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
3
Alternative for wasmer inspect
#1554 opened May 12, 2024 by svanimpe
1
wasm-tools print --skeleton with no core modules
#1527 opened May 2, 2024 by rylev
Compose example fails
#1502 opened Apr 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
9
wasmparser::validator::ComponentState::validate_and_register_named_types should return Result instead of bool
#1486 opened Apr 4, 2024 by rylev
Add a top-down code generation option to wasm-smith wasm-smith Related to the wasm-smith crate and creating wasm modules for fuzzing
#1484 opened Apr 3, 2024 by fitzgen
json-from-wast: differences to wabt's wast2json
#1471 opened Mar 27, 2024 by ohorn
3
wit-component: Reactors should call _initialize
#1464 opened Mar 20, 2024 by ospencer
2
Don't require the wit/ root directory to contain a package
#1462 opened Mar 19, 2024 by lann
Relax WIT directory structure
#1461 opened Mar 19, 2024 by lann
"component is not compatible with import" error is returned when combining components with resources using dependencies
#1452 opened Mar 13, 2024 by andrzejressel
Support relaxed kebab case for filenames in compose
#1440 opened Mar 8, 2024 by nuke-web3
7
wit-parser: parse multiple packages and automatically resolve
#1433 opened Mar 1, 2024 by oovm
1
ProTip! Type g i on any issue or pull request to go back to the issue listing page.