Stream: git-wasmtime

Topic: wasmtime / issue #4105 Expose `TrapCode::Interrupt` on ep...

view this post on Zulip Wasmtime GitHub notifications bot (May 09 2022 at 14:21):

alexcrichton commented on issue #4105:

Using the Interrupt trap code here seems reasonable to me, but instead of discarding the trap that's returned could the insertion and customization of the TrapCode be done when the trap is first created? (e.g. in the new_epoch handler within wasmtime)

view this post on Zulip Wasmtime GitHub notifications bot (May 09 2022 at 22:56):

saulecabrera commented on issue #4105:

Thanks for the feedback @alexcrichton! I agree, that's a much cleaner solution, I had overlooked this approach due a misunderstanding in the relationship between anyhow::Error and wasmtime::Trap.

view this post on Zulip Wasmtime GitHub notifications bot (May 09 2022 at 23:17):

github-actions[bot] commented on issue #4105:

Subscribe to Label Action

cc @peterhuene

<details>
This issue or pull request has been labeled: "wasmtime:api"

Thus the following users have been cc'd because of the following labels:

To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.

Learn more.
</details>

Last updated: Dec 06 2025 at 06:05 UTC