You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
wasm cannot easily reference external memory regions, since each instance is guaranteed to be a sandboxed region of memory.
To solve this limitation, there is a feature spec that supports reference types.
I am particularly interested in the EXTERNREF keyword.
But now, it seems that most of them have been introduced in a limited way only in the web environment. find the methods using in our VM.
The text was updated successfully, but these errors were encountered:
* feat: add #[callable_point] proc macro
* feat: add #[dynamic_link] proc macro
* fix: publiclize the memory module
using in #[callable_point] and #[dynamic_link]
* feat: add re-exports #[callable_point] and #[dynamic_link]
* feat: make tuple return by #[callable_point] and #[dynamic_link]
* feat: add copies region of args and return between env
The actual copy calls are executed by wasmvm.
* fix: disable return the tuple type
#156
* refactor: improve error handling with proc_macro_error
* feat: update sample contract for dynamic_link
* test: add unit test for copy_region_vals_between_env
* test: add integration test for callable_point macro
proc_macro cannot do normal unit tests.
Instead, it is replaced by the contract's integration test.
* test: add integration test for dynamic_link macro
proc_macro cannot do normal unit tests.
Instead, it is replaced by the contract's integration test.
* fix: unlimit the target_arch of memory module
When running the test with dynamic_link proc_macro,
it should be able to compile the memory module on other architectures as well.
* chore: cargo fmt
* chore: update cargo.lock for contracts
* fix: fix maximum size
* chore: cargo clippy
* test: add module name test condition for dynamic_link macro
* chore: fix reverted unused warnings in the contracts
* chore: fix typo
* chore: remove unnecessary prefix
* refactor: improve abort message
* refactor: change to use quote! and proc_macro2
proc_macro2 allows the implementation of separate modules.
* chore: update cargo.lock
* chore: disable clippy warning for abort_by!
* fix: add disallowed type by parameter
see: #152
* chore:cargo fmt
* chore: avoid false-positive of clippy
* chore: again avoid clippy
* chore: fix typo
Closes: #151
wasm cannot easily reference external memory regions, since each instance is guaranteed to be a sandboxed region of memory.
To solve this limitation, there is a feature spec that supports reference types.
I am particularly interested in the
EXTERNREF
keyword.But now, it seems that most of them have been introduced in a limited way only in the web environment. find the methods using in our VM.
The text was updated successfully, but these errors were encountered: