-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add import&export macro and serialized data copy pass #157
feat: add import&export macro and serialized data copy pass #157
Conversation
a3b068b
to
b5da1ff
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are many format!
to make code strings. Use quote!
instead of them.
https://doc.rust-lang.org/proc_macro/macro.quote.html
using in #[callable_point] and #[dynamic_link]
The actual copy calls are executed by wasmvm.
proc_macro cannot do normal unit tests. Instead, it is replaced by the contract's integration test.
proc_macro cannot do normal unit tests. Instead, it is replaced by the contract's integration test.
When running the test with dynamic_link proc_macro, it should be able to compile the memory module on other architectures as well.
e5b2b9e
to
f6c4ca9
Compare
force pushed because it based on PR #153, and PR#153 is squash merged now. |
proc_macro2 allows the implementation of separate modules.
I refactored that using the |
Description
Closes #153
#[callable_point]
that supports the easy function export and deserialize passed args internally.#[dynamic_link]
that supports the easy function import and serialize the passing args internally.please note:
And, Please The
dynamic_link
poc PR(#153) first. This PR is based on #153.#153 must be merged first before this PR can be reviewed.
Types of changes
Checklist