Skip to content

Navigation Menu

Appearance settings

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

Appearance settings

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

rust-lang / rust-clippy Public

Notifications You must be signed in to change notification settings
Fork 1.7k
Star 12.1k

Code
Issues 2.2k
Pull requests 143
Discussions
Actions
Projects
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Wiki
Security
Insights

Add lint to tell about let else pattern#8437

Merged

bors merged 11 commits intorust-lang:masterrust-lang/rust-clippy:masterfrom

est31:let_else_lintest31/rust-clippy:let_else_lintCopy head branch name to clipboard

Oct 24, 2022

Conversation Commits11 (11)Checks Files changed

Commits

Commits on Oct 24, 2022

Add lint to tell about let else pattern
est31
committed
Also support linting for match
est31
committed
Support tuples
est31
committed
Don't suggest let else in match if the else arm explicitly mentions non obvious paths
est31
committed
Replace from_different_macros with equivalent and simpler check
est31
committed
Make the match checking configurable
est31
committed
Make an attempt of creating suggestions
est31
committed
Don't lint if the let is already a let-else

oxalica
authored and
est31
committed
Don't fire the lint if there is a type annotation
est31
committed
Fix dogfooding
est31
committed
Also consider match guards for divergence check
est31
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.