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 275 commits into
base: develop
Choose a base branch
from
Draft

Clarity Wasm #4756

wants to merge 275 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.

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.
For an `optional`, do not try to create a value unless the indicator is
`1`. Similarly, for `response`, do not try to create a value from the
`ok` value if the indicator is `0` or from the `err` value if the
indicator is `1`.
@obycode
Copy link
Contributor

obycode commented Jul 31, 2024

Let's get any failing tests working again in this branch.

Acaccia and others added 22 commits August 2, 2024 13:59
…ynamic

Clarity-Wasm: fix for the `contract-call?` host function
Clarity-Wasm: fix for the print host function
…se-fn

Clarity-Wasm: avoid using testing-gated parse function
…rg-error

Clarity-Wasm: add error mapping for already used arg error
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