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 #4756

Draft
wants to merge 308 commits into
base: develop
Choose a base branch
from
Draft

Clarity Wasm #4756

wants to merge 308 commits into from

Conversation

hugocaillard
Copy link
Collaborator

@hugocaillard hugocaillard commented May 7, 2024

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.

obycode and others added 30 commits November 27, 2023 19:53
This is the return value from the last expression at the top-level of
the contract.
There are now tests for the functions that read and write the Wasm
memory!
This includes `keccak256`, `sha512`, and `sha512/256`.
This function is useful for debugging wasm code.
This code can still use some improvements and DRYing up.
Even when called as a local function (within the same contract), public
functions will have their changes rolled back if they return an error.
…ontract-calls

feat(wasm): include proper rollback handling for contract-calls
csgui and others added 30 commits October 9, 2024 19:53
chore: sync host functions with clarity-wasm implementation
Add stub for `debug_msg` in linker
fix: correct error mapping for BadTypeConstruction
Update Cargo.lock on feat/clarity-wasm-develop
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants