fitzgen opened PR #13083 from fitzgen:component-linker-fallible-allocs to bytecodealliance:main:
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
fitzgen requested dicej for a review on PR #13083.
fitzgen requested wasmtime-core-reviewers for a review on PR #13083.
alexcrichton submitted PR review:
Tests too?
alexcrichton created PR review comment:
I forget the exact purpose of this, but could this switch to
StringPool? Otherwise the purpose of theArcwas to avoid cloning it when inserting into two lists which this is doing away with. I think though thatStringPoolprobably subsumes this?
fitzgen commented on PR #13083:
Tests too?
I have a bunch of OOM tests coming in follow ups, but wanted to separate this into its own PR first so reviewers could focus on actual code changes.
I can pluck them out and and them to this PR if you prefer tho
fitzgen commented on PR #13083:
(Figured that existing tests passing was enough tire-kicking for this PR to land on its own)
fitzgen updated PR #13083.
fitzgen has enabled auto merge for PR #13083.
alexcrichton commented on PR #13083:
Nah no worries, so long as there's tests eventually :+1:
fitzgen added PR #13083 Make component linker allocations fallible to the merge queue.
fitzgen merged PR #13083.
fitzgen removed PR #13083 Make component linker allocations fallible from the merge queue.
Last updated: May 03 2026 at 22:13 UTC