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.

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

Unpin clap dependency #803

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Unpin clap dependency #803

wants to merge 1 commit into from

Conversation

jhpratt
Copy link

@jhpratt jhpratt commented Aug 7, 2024

I'm unable to see why this was pinned in the first place. As pinning is unidiomatic and causes unexpected build failures, let's unpin it.

@waywardmonkeys
Copy link
Contributor

If you look at the history for that line, you'll see this was done in #768 because of MSRV issues.

If you want to unpin this, then it would be better to add Cargo.lock (remove it from .gitignore as well) and have Cargo.lock use versions that are compatible with our MSRV.

@jhpratt
Copy link
Author

jhpratt commented Aug 12, 2024

I've done just that. Committing Cargo.lock is considered best practice in Rust nowadays regardless 🙂

@jayvdb jayvdb mentioned this pull request Sep 8, 2024
@kaivol
Copy link

kaivol commented Nov 28, 2024

Are there any plans to merge this PR?

The current situation makes it impossible to use criterion in a cargo workspace where newer versions of clap are used.

@lemmih
Copy link
Collaborator

lemmih commented Nov 29, 2024

Need someone to review this PR.

@waywardmonkeys
Copy link
Contributor

@lemmih This PR is fine as-is, and then we can do follow ups to potentially update the Cargo.lock some and perhaps evaluate what the current MSRV should be.

@waywardmonkeys
Copy link
Contributor

(I didn't look at the actual current contents of the Cargo.lock and assumed it was valid.)

@jhpratt
Copy link
Author

jhpratt commented Nov 29, 2024

I assure you that the Cargo.lock was auto-generated at the time of opening the PR. I have no doubt that there are things out of date in it by now, however. It's trivial to regenerate it from scratch if preferred.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants