Skip to content

Conversation

@arjunr2
Copy link
Collaborator

@arjunr2 arjunr2 commented Nov 14, 2025

Notes

  • Support for all entrypoints through Func, TypedFunc, and ComponentFunc
  • Support for all component builtins
  • Support for all instantiation entrypoints
  • Support for both sync and async
  • Fully embedding agnostic replay driver

Structure

  • All core capabilities are feature-gated with the rr feature. The only things exposed without the feature are rr::hooks, which offers convenient methods to hook recording/replaying mechanisms into the rest of the engine.
    As a result, rr without hooks should be able to land with no impact on existing Wasmtime whatsoever.

Observed overheads

Between 4-8%

alexcrichton and others added 30 commits August 6, 2025 13:55
Helps get some binaries to test with
Things left to complete:
* Core wasm support
* Improved error handling
* Wasmtime CLI integration
@arjunr2 arjunr2 mentioned this pull request Nov 14, 2025
Copy link
Member

@cfallin cfallin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is generally pretty good -- thanks a bunch for all of your hard work here!

I have a ton of nits below but I don't think there is anything fundamentally wrong with any of the design. This is more a lot of polish and getting details right.

My eyes did glaze over at several parts around macro usage, and innards of the component ABI. Definitely will need careful review by Alex and/or others when this lands for real. But this should be a start at least. Happy to discuss any of the below.

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.

4 participants