-
Notifications
You must be signed in to change notification settings - Fork 663
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
Clarity Wasm #4756
Draft
hugocaillard
wants to merge
267
commits into
develop
Choose a base branch
from
feat/clarity-wasm-develop
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Clarity Wasm #4756
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
All error cases should be properly handled and generate an error to be handled by the caller. Any `Wasm` errors should never happen in production and would indicate an implementation problem if they show up.
Co-authored-by: Acaccia <[email protected]>
This is to allow moving stacks-blockchain into clarity-wasm as a submodule.
Also adds better support for `buff` type
This latest iteration allows a clean mechanism for the initialization functions to get mutable access to the `contract_context` while limiting the runtime functions to immutable access, without requiring lots of duplicated code.
This was originally necessary with the previous restructuring of the Wasm context objects, but is no longer needed, so it's better to do everything at once again.
…t-to-wasm Clarity-Wasm: Implement "pass_argument_to_wasm" for remaining types
…th-for-workspace-dependencies refactor: use relative path for workspace dependencies
…-develop Merge develop into clarity-wasm branch
…-develop Merge develop into clarity-wasm develop branch
Let's get any failing tests working again in this branch. |
…alue in a serialized tuple
…emap-patch add methods to TypeMap
…ynamic Clarity-Wasm: fix for the `contract-call?` host function
…p-merge Merging latest develop
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This contains the changes used for clarity-wasm. It may not yet be ready to be merged, but the clarity-wasm team is reviewing it as we go and then it will need a thorough review once it is ready to be merged into next.
This branch supersedes #3880, #4093, and the previous branch that was used by clarinet. The clarinet specific changes (to make the clarity crate compilable to wasm) are the starting point for the clarity-wasm changes.