[fix] the suspicious use of OpenOptions::create() without an explicit OpenOptions::truncate(). #468
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Rust 1.77 introduces a new cargo clippy lint rule for the suspicious use of
OpenOptions::create()
without an explicitOpenOptions::truncate()
, which failed thecargo clipy
CI taskMotivation and Context
Dependencies
None
Type of change
Please delete options that are not relevant.
How has this been tested?
cargo clippy -p rspotify -p rspotify-http -p rspotify-model -p rspotify-macros --no-default-features --features=rspotify/cli,rspotify/env-file,rspotify/client-ureq,rspotify/ureq-rustls-tls,rspotify-http/client-ureq,rspotify-http/ureq-rustls-tls --all-targets -- -D warnings
: passedIs this change properly documented?
It's unnecessary.