-
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
Prefixed crate names with zksync_consensus_ #25
Conversation
@@ -28,7 +28,7 @@ jobs: | |||
path: "protobuf" | |||
- uses: mozilla-actions/[email protected] | |||
- name: build test | |||
run: cargo build -p schema --bin conformance_test | |||
run: cargo build -p zksync_consensus_schema --bin conformance_test |
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.
Off-topic (?): If we want to publish crates, I'd suggest to move this binary target to an example or a separate crate, so that it doesn't bring unnecessary extra deps (e.g., Tokio) as direct deps of the library. The same can be said about testonly
modules in various crates (they may bring extra deps such as rand
as well); so it would be better to gate this functionality behind an opt-in feature. Can be done later, of course.
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 would prefer to minimize the usage of the feature flags if possible. I don't know much about the crate publishing standards though.
Prefixed crate names with zksync_consensus_ to make the names more scope specific.
We cannot afford keeping the generic names we used so far, as this repo will be used in zksync-era now.
The exception is zksync_concurrency (not zksync_consensus_concurrency) which is intended to be extracted from this repo eventually.