github-actions[bot] commented on Issue #1781:
Subscribe to Label Action
cc @bnjbvr, @fitzgen, @peterhuene
<details>
This issue or pull request has been labeled: "cranelift", "cranelift:wasm", "fuzzing", "lightbeam", "wasmtime:api", "wasmtime:c-api"Thus the following users have been cc'd because of the following labels:
- bnjbvr: cranelift
- fitzgen: fuzzing
- peterhuene: wasmtime:api, wasmtime:c-api
To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.
Learn more.
</details>
fitzgen commented on Issue #1781:
Alright, I was missing some C API changes, but I've added them, and CI is green now.
fitzgen commented on Issue #1781:
Alright, I believe I've addressed all of your review feedback and discussed the cases where I haven't (host info).
Want to take another look @alexcrichton?
github-actions[bot] commented on Issue #1781:
Subscribe to Label Action
cc @fitzgen
<details>
This issue or pull request has been labeled: "cranelift:area:peepmatic"Thus the following users have been cc'd because of the following labels:
- fitzgen: cranelift:area:peepmatic
To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.
Learn more.
</details>
fitzgen commented on Issue #1781:
One thing I wanted to point out, though. We talked a bit about how host info is useful becuase it has the same lifetime of the
ExternRef, but I'm not actually seeing where that happens? If youset_host_infofor something, I don't see a destructor ofExternRefwhich the calls the finalizer when theExternRefgoes away. (I think this just happens when theStoregoes away?)Yeah, this is why it is useful at the API level. Our implementation doesn't do that yet :sweat_smile:
Last updated: Dec 13 2025 at 19:03 UTC