bytecodealliance / bytecodealliance/wasmtime

What is the reason for the `V128` formatting in Wasmtime's CLI?

Open
#10,486 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
18.6k
Forks
1.8k
Avg merge
1d 19h
Merged PRs (30d)
121

Description

When Wasmtime's CLI returns a `v128` value, it is formatted as `u128` value.
In Wasmi I have made some thoughts about the formatting of `v128` values and came to the conclusion that it is probably best to format it as hex-dec number with leading zeros. For example: `0x006E006E61635F6E61635F6E61635F6E`

Was there a specific reason Wasmtime chose to format `v128` as a simple `u128`?

Ideally Wasmi has the same formatting as Wasmtime (or more generally: Wasm runtimes share the same formatting), but at this point I find the `u128` formatting to be very weird and thus I suppose I am missing something here.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.