Skip to content

Navigation Menu

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.

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 Public

Notifications You must be signed in to change notification settings
Fork 12.8k
Star 99.5k

Code
Issues 5k+
Pull requests 628
Actions
Projects 7
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

More accurately point to where default return type should go#116296

Merged

bors merged 4 commits intorust-lang:masterrust-lang/rust:masterfrom compiler-errors:default-returncompiler-errors/rust:default-returnCopy head branch name to clipboard

Oct 5, 2023

+105-89

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Oct 4, 2023

Point to where missing return type should go
compiler-errors
committed
Fix clippy
compiler-errors
committed
Point to closure return instead of output if defaulted
compiler-errors
committed
Fix spans for comments in rustfmt
compiler-errors
committed

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.