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 13.2k
Star 102k

Code
Issues 5k+
Pull requests 747
Actions
Projects 9
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Suggest deref when coercing `ty::Ref` to `ty::RawPtr`#71540

Merged

bors merged 3 commits intorust-lang:masterrust-lang/rust:masterfrom ldm0:ref2ptrldm0/rust:ref2ptrCopy head branch name to clipboard

Apr 30, 2020

Conversation Commits3 (3)Checks Files changed

Commits

Commits on Apr 29, 2020

Move branch point upwards to avoid unnecessary mk_ptr()
ldm0
committed
Rename function to suggest_deref_ref_or_into because it's suggesting
ldm0
committed
Suggest deref when coercing ty::Ref to ty::RawPtr
ldm0
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.