Skip to content
This repository has been archived by the owner on Oct 31, 2023. It is now read-only.

chore: use WASMValue for wasm arguments as well as return values #157

Merged
merged 1 commit into from
May 5, 2023

Conversation

TomAFrench
Copy link
Member

This PR splits off @phated's change from #151 to use WASMValue for wasm arguments as well as for return values.

Co-authored-by: Blaine Bublitz <blaine.bublitz@gmail.com>
@TomAFrench TomAFrench requested a review from phated May 5, 2023 11:13
@phated phated added this pull request to the merge queue May 5, 2023
Merged via the queue into master with commit 4436b54 May 5, 2023
@phated phated deleted the wasmvalue-into branch May 5, 2023 15:11
TomAFrench added a commit that referenced this pull request May 12, 2023
* acvm-0.12.0:
  fix bad rebase
  chore: Release 0.1.2 (#183)
  fix: Remove star dependencies to allow publishing (#182)
  chore: Release 0.1.1 (#181)
  fix: Add description so crate can be published (#180)
  chore: update readme to new name and add contract note (#177)
  feat!: update to acvm with non-homogeneous bb calls (#169)
  update to latest changes
  chore: Release 0.1.0 (#173)
  use patch syntax
  chore: update to use new black box solver interface
  feat!: update to target acvm-84b5d18d
  chore(ci): Update tokens (#174)
  chore: Add release-please and publish workflows to project (#172)
  feat!: Update to ACVM v0.11.0 (#151)
  chore: remove usage of `std::mem::forget` (#164)
  chore: Enforce proper conversion of memory into fixed length array (#163)
  chore: Add test for Keccak256 constraint (#158)
  chore: use `WASMValue` for wasm arguments as well as return values (#157)
  feat!: Add Keccak constraints (#150)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants