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.

Sign up

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.3k
Star 103k

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

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Safe Transmute: Use 'not yet supported', not 'unspecified' in errors#122560

Merged

bors merged 2 commits intorust-lang:masterrust-lang/rust:masterfrom

jswrenn:not-yet-supportedjswrenn/rust:not-yet-supportedCopy head branch name to clipboard

Mar 15, 2024

Conversation Commits2 (2)Checks Files changed

Commits

Commits on Mar 15, 2024

Safe Transmute: Use 'not yet supported', not 'unspecified' in errors
jswrenn
committed
Safe Transmute: lowercase diagnostics
jswrenn
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.