Dan Gohman

The Cray 1's SIMD was variable-length; registers had a maximum length, but the machine could use any length up to that maximum. Today's AVX152, ARM SVE, and even GPUs could...

> C++ guest support C++ language support #826 > symmetric C++ API (I think the old one is horrible to understand, because move semantic for arguments is alien to C++)...

cargo component itself uses the Rust wasm32-wasip1 target to produce core Wasm modules, and applies the component adapter to produce Wasm components. It doesn't currently work with the wasm32-wasip2 target.

There are ways to test for things like "v6" vs "v7", for example `all(target_arch = "arm", target_feature = "v7")`. I wonder if that goes far enough.

I've now released cap-std 2.0.2, which I expect fixes this for 2.x users. From the error message, it appear you're using cap-std 1.x. I have started to look into backporting...

Backporting the fix to cap-std 1.x is too complex due to the MSRV of 1.56. I think it's best if users needing support for newer Rust versions to update to...

Such a `Dir` would not be able to implement [`from_std_file`](https://docs.rs/cap-std/latest/cap_std/fs/struct.Dir.html#method.from_std_file), [`as_raw_handle`](https://docs.rs/cap-std/latest/x86_64-pc-windows-msvc/cap_std/fs/struct.Dir.html#impl-AsHandle-for-Dir), and similar things in the current `Dir` API. Would it make sense for the functionality of a "root of...

Worlds aren't things you can select individual things from to import/export, because world items already have committed to being import or export. You can include the entire contents of one...

> Thanks! Are there any ongoing proposals for top-level functions? I'm not aware of any currently. > > You can include the entire contents of one world into another though...

@kripken With the updates above, can this issue now be closed?