Problem
Our binary parser relies on the third-party Wasm interpreter py-wasm, which has not been maintained since 2019. Since then, the Wasm specification has evolved, introducing new instructions (#523) and possibly other features not supported by py-wasm. This issue is particularly critical as it blocks us from upgrading the Rust compiler version, which relies on these new instructions.
Temporary solution
To address this issue, we have decided to fork py-wasm and implement the missing instructions ourselves.
Long-term goal
Our ultimate goal is to identify a well-maintained third-party package developed by a reliable organization or company that can be adopted as a replacement.
Action Items
- Forking and Implementation: We will fork py-wasm to our repository and implement missing instructions to maintain compatibility with the latest Wasm specifications.
- Search for Alternatives: Concurrently, we are actively searching for alternative, well-maintained Wasm binary parser packages to replace py-wasm in the long term.
Problem
Our binary parser relies on the third-party Wasm interpreter
py-wasm, which has not been maintained since 2019. Since then, the Wasm specification has evolved, introducing new instructions (#523) and possibly other features not supported bypy-wasm. This issue is particularly critical as it blocks us from upgrading the Rust compiler version, which relies on these new instructions.Temporary solution
To address this issue, we have decided to fork py-wasm and implement the missing instructions ourselves.
Long-term goal
Our ultimate goal is to identify a well-maintained third-party package developed by a reliable organization or company that can be adopted as a replacement.
Action Items