-
Notifications
You must be signed in to change notification settings - Fork 136
Update dependencies and bump to Rust 1.80 #450
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
Conversation
This is actually rust-lang/rust-clippy#12856 But the code was a bit of a smell: `&&mut PathBuf`
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.
LGTM, but I'd probably change the title, such that it also reflects the other package updates
Cargo.toml
Outdated
# Remove assigning_clones once it's allowed by default in stable Rust | ||
# https://github.com/rust-lang/rust-clippy/pull/12779 |
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.
Why all the comments (including below)?
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.
Oh seriously? I trusted cargo upgrade
to actually do the right thing. That's incredibly annoying.
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.
Ok, that's a weird, probably open an issue in cargo upstream then?
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.
It's part of cargo-edit. I believe that the in-place toml editing doing stupid things with comments/ordering is known, although I can't find where it's tracked at the moment.
Why bundle the update to Rust with the other? (Just asking.) |
This is the policy we decided upon in linebender/rfcs#5 |
I believe he meant, why not separate PRs for package-updates and rust-version, but I think having all of this in one PR is good for me too, as those update changes seem to be largely uncontroversial/maintenance |
There is one "semi-false-positive" lint triggered, which I have fixed.
Otherwise, the required