feat: passing wasm as via ptr and len in manifest, revamp extism::Wasm #17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding support of extism/extism#657
Manifest::json
by default is self contained (serialized wasm as base64). Passfalse
to instead getWasmBytes
encoded as ptr and length.WasmBytes
is now much more flexible, it still can store a copy of the wasm, but can also instead use a smart pointer.Deprecated the
Wasm
constructor usingWasmSource
asstd::variant
is now used to manage the types.Manifest
can now be constructed with wasm(s).