Skip to content
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 Next #4093

Closed
wants to merge 176 commits into from
Closed

Clarity Wasm Next #4093

wants to merge 176 commits into from

Conversation

obycode
Copy link
Contributor

@obycode obycode commented Nov 28, 2023

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 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.

Ludo Galabru and others added 30 commits November 22, 2023 18:27
Crate already pulled by the clarity vm crate, and only used there.
Handle passing arguments into a contract call using the Wasm runtime and
handle returning a value from the contract call.
The pass that initializes a contract should have the contract analysis
available, but when a contract is being called, only use the
`ContractContext`. This requires adding the return type of a function to
this context.
This comment clarifies that this function should not be used during
normal execution.
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 <anthonycaccia24@gmail.com>
This is to allow moving stacks-blockchain into clarity-wasm as a
submodule.
@hugocaillard hugocaillard changed the title Clarity Wasm Clarity Wasm Next May 7, 2024
@hugocaillard
Copy link
Collaborator

Superseded by #4756
I'll close this one once stacks-network/clarity-wasm#400 is merged

@hugocaillard hugocaillard mentioned this pull request May 7, 2024
@hugocaillard hugocaillard deleted the feat/clarity-wasm-next branch July 12, 2024 14:10
@blockstack-devops
Copy link
Contributor

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Oct 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants