jrandolf edited PR #14916.
github-actions[bot] added the label wasi on PR #14916.
github-actions[bot] added the label wasmtime:api on PR #14916.
pchickey commented on PR #14916:
I can't think of any reason a user might want to import wasi:io as a named import, or that an embedding would provide it as one. wasi:io is a singleton and so there being another instance of the same interface is nonsensical.
In general I see the wasip2 interfaces and implementations as being "done" and only getting bug fixes, and we are focusing all our energy for new development on wasip3. So, in general, I would require significant convincing that any of the p2 interfaces should be made compatible with named imports, even if unlike wasi:io they aren't a special case that should always be singular.
pchickey edited a comment on PR #14916:
I can't think of any reason a user might want to import wasi:io as a named import, or that an embedding would provide it as one. wasi:io is a singleton and so there being another instance of the same interface is nonsensical.
In general I see the wasip2 interfaces and implementations as being "done" and only getting bug fixes, and we are focusing all our energy for new development on wasip3. So, in general, I would require significant description of a real use case motivating that any of wasmtime's implementations of the p2 interfaces should be made compatible with named imports, even if unlike wasi:io they aren't a special case that should always be singular.
jrandolf commented on PR #14916:
Actually, this was an example listed in the spec which is why I added it. I also do not think it's needed. I think we can close this if everyone is on the same page
:cross_mark: pchickey closed without merge PR #14916.
Last updated: Oct 31 2026 at 23:03 UTC