-
Notifications
You must be signed in to change notification settings - Fork 368
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
Make supernova-benches an independent workspace #44
Conversation
For a cleaner solution: move exclude = ["supernova-benches"] to Cargo.toml. (because of rust-lang/cargo#6745) Benefits are:
Later, we could change it to exclude = ["benches/*"] |
Awesome, thanks for the great explanation @slumber. I've followed through with the proposed fix. |
supernova-benches/Cargo.lock
Outdated
@@ -0,0 +1,1611 @@ | |||
# This file is automatically @generated by Cargo. |
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.
Opposite to the workspace, I believe this one is OK (or rather should) to be excluded.
I wouldn't expect people to always update it along with the main lock file, as it's not going to be done automatically for an excluded crate.
So it's better to add .gitignore
to the crate with Cargo.lock
* make supernova-benches an independent workspace * place supernova-benches at root, and exclude from workspace * rm Cargo.lock from git
* make supernova-benches an independent workspace * place supernova-benches at root, and exclude from workspace * rm Cargo.lock from git
One can't run
supernova-benches
, as it now thinks it is part of the zkVM workspace after the recentsupernova
->nexus-zkvm
migration.This fixes this.