jameysharp commented on issue #6937:
I'm handing review of this off to Alex as the author of the API you're extending.
I had hoped that the
from_trusted_file
entry-point or similar would suffice to avoid embedders needing to detect for themselves whether they were holding on to a precompiled module. However, it sounds like both of you have reasons why that wasn't enough. I don't want to think about it that hard so I'll leave you to it.
github-actions[bot] commented on issue #6937:
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:
- peterhuene: wasmtime:api
To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.
Learn more.
</details>
acfoltzer commented on issue #6937:
I'm still getting acquainted with the component side of the crate API, but it seems like a
ModuleOrComponent
type is going to be necessary on the client side for pretty much any transitional project. If the expectation is that most applications will eventually move to the component model, I don't think it's worth codifying that sort of type in the crate API. But if you're feeling the pain while maintaining the CLI as well, it might be worth thinking more about some shared interfaces.
Last updated: Dec 23 2024 at 12:05 UTC