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

Clarity Wasm #4756

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

hugocaillard and others added 30 commits December 4, 2023 17:38
Previously, we used 4 bytes, but only 1 byte is necessary.
This was fixed in #3945, but somehow got overwritten in this branch.
Annoyingly, we need to do this everytime we modify this repo until we
come up with a better way to satisfy these interdependencies between
clar2wasm and stacks-core.
This field is removed when not in `developer-mode`. This changeset
ensures that the clarity module can build correctly when
`developer-mode` is not enabled.

See #3945
Something went wrong with the merges of changes from PR #3955 into
`next` and this issue re-surfaced.
csgui and others added 30 commits October 29, 2024 10:54
Update feat/clarity-wasm-develop branch
Instantiating a `wasmtime::Engine` is an expensive operation, so it is
best to do it only once for the duration of a `GlobalContext`. Cloning
an engine is, however, not an expensive operation (just an `Arc::clone`)
and we use it to avoid referring to the global context already referred
to by the instantiated `ClarityWasmContext`.

See-also: stacks-network/clarity-wasm#468
feat(wasm): use only one `Engine` per global context
…ons_to_trait

add missing functions to trait
…(burn)-block-info-linker-fn

Split `get-(burn)-block-info` linker function
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.