Skip to content

Conversation

@alexcrichton
Copy link
Member

Support nested components insofar as they don't have access to modules at this time. This helps wasmtime wizer support wasm-tools-generated components which use nested components for type-ascribing exports. Otherwise though nested components are not allowed to defined or instantiate core modules as that would need more implementation in Wizer to support.

@alexcrichton alexcrichton requested a review from a team as a code owner October 21, 2025 19:10
@alexcrichton alexcrichton requested review from dicej and removed request for a team October 21, 2025 19:10
Support nested components insofar as they don't have access to modules
at this time. This helps `wasmtime wizer` support wasm-tools-generated
components which use nested components for type-ascribing exports.
Otherwise though nested components are not allowed to defined or
instantiate core modules as that would need more implementation in Wizer
to support.
@alexcrichton alexcrichton force-pushed the wizer-nested-component branch from 08d5046 to 358a03b Compare October 21, 2025 19:46
@alexcrichton alexcrichton added this pull request to the merge queue Oct 21, 2025
Merged via the queue into bytecodealliance:main with commit 155f827 Oct 21, 2025
45 checks passed
@alexcrichton alexcrichton deleted the wizer-nested-component branch October 21, 2025 21:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants