refactor: bypass serialized cache in wasmer_wamr flag #119
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.
With the
wasmer_wamr
flag, there is no utility to caching serialized wasms as they are not pre-compiled.Attempting to use a previously pre-compiled wasm with the flag
wasmer_wamr
will fail. This could possibly arise if a user caches some wasms to holochain data directory from a holochain conductor withwasmer_sys
enabled, and then attempts to use the same data directory in a conductor withwasmer_wamr
enabled.This PR modifies the ModuleCache and SerializedModuleCache to simply bypass actual caching functionality with the feature flag
wasmer_wamr