Additional `import`s in generated component about cargo-component

[peterhuene]

You are correct that, by default, certain WASI interfaces are automatically imported based upon the component's use of the Rust stdlib.

It is possible to avoid this by not using the wasm32-wasi target (which is the default target of cargo-component).

If you pass --target wasm32-unknown-unknown, the component will not import any WASI interfaces, by default, but it still may import any WASI interfaces that were explicitly imported by the target world.

[kaivol]

Thanks for the reply, that clears things up for me!

However, I was a little surprised that the wasm32-unknown-unknown target also supports the standard library, even though most (all?) APIs seem to be non-functional.
Do you happen to know why it was originally decided to implement the standard library for this target? As I understand it, wasm32-unknown-unknown would be a prime candidate for a #![no_std] target.