Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Is a single Cargo.lock for the whole workspace OK? #64

Open
anp opened this issue Nov 2, 2018 · 0 comments
Open

Is a single Cargo.lock for the whole workspace OK? #64

anp opened this issue Nov 2, 2018 · 0 comments

Comments

@anp
Copy link
Owner

anp commented Nov 2, 2018

#63 (comment)

If transitive dependencies of benchmark crates get changed when we add new benchmarks, should we have to invalidate past results? Can we "firewall" the benchmark crates' dependencies from each other while still having them able to use the local support crates?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@anp