rust-lang / rust-lang/rust-clippy
"clippy-driver -Vv" is different from "clippy-driver --version --verbose"
Open
Nobody has claimed this yet.
C-bug
C-enhancement
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
These two invocations produce the same output:
$ clippy-driver -V
clippy 0.0.212 (69f99e7 2019-12-14)
$ clippy-driver --version
clippy 0.0.212 (69f99e7 2019-12-14)
But these do not. Assuming that -v is the short form for --verbose, I would expect them to be equivalent. I would also expect -Vv to be the same as -V -v.
$ clippy-driver -Vv
rustc 1.41.0 (5e1a79984 2020-01-27)
binary: rustc
commit-hash: 5e1a799842ba6ed4a57e91f7ab9435947482f7d8
commit-date: 2020-01-27
host: x86_64-unknown-linux-gnu
release: 1.41.0
LLVM version: 9.0
$ clippy-driver --version --verbose
clippy 0.0.212 (69f99e7 2019-12-14)
[jsgf@jsgf-fedora-R90S9GAX rustversion]$ clippy-driver -V -v
clippy 0.0.212 (69f99e7 2019-12-14)
Is this intended? It's very confusing.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the clippy-driver entry point and run the reported -Vv, --version --verbose, and -V -v invocations to compare their output. Done means the combined short and long forms produce the same version information, with regression coverage for the reported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100