-
Notifications
You must be signed in to change notification settings - Fork 39
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
Zero bin merge #279
Zero bin merge #279
Conversation
- Also manually sorted dep names.
- Switched all internal deps to use workspace deps where possible. - Also needed to move `zero_bin/common` --> `zero_bin/zero_bin_common` because having a dep name of just "common" wasn't really clear that this dep was just for `zero-bin`.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank a bunch @BGluth!
Additionally now that zero-bin is here, we should remove Cargo.lock
from .gitignore
.
serde_json = { workspace = true } | ||
|
||
# Local dependencies | ||
mpt_trie = { version = "0.3.0", path = "../mpt_trie" } | ||
mpt_trie = { workspace = true } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any reason why the version is removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mistake, I'll re-add this, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually yeah I was missing version
in the root Cargo.toml
, but here I think we can just use workspace = true
since it will pull from that version (I think right?).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's easier for version publishing to have version numbers. But regardless, I don't understand why it would complain now for crates that were already here before?
- Also a `clippy` pass.
AArgh, I had mentioned to remove |
Sorry about that! That was the one that I missed... |
- Something happened in the merge `zero_bin` PR (#279) where a local-renamed dep (something that is not on `crates.io`) got set just with a semver. Somehow `Cargo` is still able to build fine (not sure how...), but `rust-analyzer` (at least on my end) fails to make it past parsing the root `Cargo.toml`. This PR fixes this issue.
Merged
zero_bin
into this repo. Also needed to change some deps around in order for everything to align (eg. some deps can now be workplace deps).zero_bin/common
is nowzero_bin/zero_bin_common
since a sub-crate calledcommon
implies that it's for the entire crate (zk_evm
) when it's really just forzero-bin
.