Replace fork of bitvec by upstream #163
Assignees
Comments
Merged
ed255
added a commit
that referenced
this issue
Sep 7, 2022
The compliation error comming from the funty dependency of bitvec isn't happening anymore, so we remove the patched dependency to the forked bitvec. Resolve #163
Merged
ed255
added a commit
that referenced
this issue
Sep 7, 2022
The compliation error comming from the funty dependency of bitvec isn't happening anymore, so we remove the patched dependency to the forked bitvec. Resolve #163
adria0
pushed a commit
to adria0/zkevm-circuits
that referenced
this issue
Sep 8, 2022
The compliation error comming from the funty dependency of bitvec isn't happening anymore, so we remove the patched dependency to the forked bitvec. Resolve privacy-scaling-explorations#163
smtmfft
added a commit
to smtmfft/zkevm-circuits
that referenced
this issue
Oct 30, 2023
…a6-release For a6 release
omega000133
pushed a commit
to omega000133/zkevm-circuits
that referenced
this issue
May 17, 2024
The compliation error comming from the funty dependency of bitvec isn't happening anymore, so we remove the patched dependency to the forked bitvec. Resolve privacy-scaling-explorations/zkevm-circuits#163
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #162 we introduce a fork of bitvec in order to solve an external dependency build error. We have a PR for upstream to solve that: ferrilab/bitvec#141. Once that PR is resolved, we can use bitvec from upstream again.
The text was updated successfully, but these errors were encountered: