Stream: git-wasmtime

Topic: wasmtime / issue #14861 Resource handles can't move betwe...

Wasmtime GitHub notifications bot (Oct 19 2026 at 20:46):

jrandolf opened issue #14861:

When a component imports the same interface under two labels and the host implements both with the same host resource type (the usual named_imports setup), passing a primary.r handle to secondary.use traps. Handle checks compare per-import resource tables, which is stricter than the spec's resource-type identity check.

Trapping here is arguably the more useful behavior since it keeps labels isolated, but it'd be good to decide and document it. The trap message is also misleading, as it calls these host resources "guest-defined": expected guest-defined resource but found a different guest-defined resource.

Wasmtime GitHub notifications bot (Oct 19 2026 at 21:01):

alexcrichton added the wasm-proposal:component-model-implements label to Issue #14861.

Wasmtime GitHub notifications bot (Oct 23 2026 at 20:55):

jrandolf commented on issue #14861:

We don't have a concrete need for this, so I'm closing it.

Wasmtime GitHub notifications bot (Oct 23 2026 at 20:55):

jrandolf closed issue #14861:

When a component imports the same interface under two labels and the host implements both with the same host resource type (the usual named_imports setup), passing a primary.r handle to secondary.use traps. Handle checks compare per-import resource tables, which is stricter than the spec's resource-type identity check.

Trapping here is arguably the more useful behavior since it keeps labels isolated, but it'd be good to decide and document it. The trap message is also misleading, as it calls these host resources "guest-defined": expected guest-defined resource but found a different guest-defined resource.

Last updated: Oct 31 2026 at 23:03 UTC