rust-lang / rust-lang/rust-clippy
Lint excessively nested or_else calls
Open
Nobody has claimed this yet.
A-lint
L-style
L-suggestion
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
A call chain like this:
func1().or_else(|_| func2().or_else(|_| func3()))
could become the less nested:
func1().or_else(|_| func2()).or_else(|_| func3())`
This avoids piling up parentheses at the end of the expression.
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
No file, test, or entry point is identified in the issue, so first locate the existing lint implementations and their tests in the repository. Done means detecting excessively nested or_else calls and accepting the flatter chained form without flagging unrelated code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100