-
Notifications
You must be signed in to change notification settings - Fork 693
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
384
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
This reverts commit b3a08fc5eb876f9e5f6797fb8fbe3c6c26bf9cf0.
This reverts commit d1aab28.
To match the behavior of the interpreter, if there are multiple top-level expressions and the last expression has no return value (e.g. a `define-` function) but an earlier expression does have a return value, the last value should be returned.
…m-develop Merge develop into feat/clarity-wasm-develop
…ompilation fix: remove unwanted compilation flag
…c-expect-error wasm generic expect error
- Updated Tokio dependency to version 1.15 with the rt-multi-thread feature enabled. - Removed from rusqlite so that it is now a required dependency.
This commit guarantees that the type-checking call is performed as expected, preventing potential issues with type validation.
Ensure context rollback in an error situation
+ simplify total bytes calculation for lists
+ compare length of the maps to ensure no extra args
…evelop Chore/clarity wasm merge develop
…ll-oom `contract-call?` fix OOM
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.