Dan Gohman

The tricky thing here is that rustix is aiming to have the same API across both the libc and linux-raw backends, and in the libc backend, it uses opendir/readdir/closedir. libc...

I find it useful to think of the rules not as "the bits might be randomized" but instead as "component-model floating-point types only have a single NaN value", with the...

Independently of what the types are named, is it desirable to allow multiple distinct NaN payloads to be observed when passing values out to non-wasm? It would seem that any...

With #279, the component-level `float32` and `float64` values are different from core-wasm `f32` and `f64`, in that they only have a single NaN value. Implementations can omit canonicalization and randomization...

Using `f32`/`f64`, and just documenting the differences, sounds good to me too.

Regardless of when we do the full switch, we should start updating tools to at least recognize `f32`/`f64` sooner rather than later. I submitted https://github.com/bytecodealliance/wasm-tools/pull/1356 to add `f32` and `f64`...

Yes. The current situation is, the wasm32-wasip2 target does a lot of things automatically, which is great and makes it easy to drop into existing Rust development workflows. But, it...

I've also now posted https://github.com/bytecodealliance/cargo-component/pull/359 to update the README text quoted above.

linux-raw-sys 0.9.3 is now released, with https://github.com/sunfishcode/linux-raw-sys/pull/153.

Thanks!