Tracking Issue for ops::Yeet (feature(try_trait_v2_yeet)) · Issue #96374 · rust-lang/rust (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Description

Feature gate: #![feature(try_trait_v2_yeet)]

This is a tracking issue for standard library additions related to #96373, which for now means the ops::Yeet struct and related impls.

It currently exists experimentally. Per the lang process, this cannot go further than experimenting without an approved RFC -- and will certainly not stabilize under the name Yeet. Please try this out and give experience reports, but be aware that it may well change drastically or be removed entirely.

Public API

// core::ops pub struct Yeet(pub E);

impl ops::FromResidual<ops::Yeet<()>> for Option; impl<T, E, F: From> ops::FromResidual<ops::Yeet> for Result<T, F>;

Steps / History

• Implementation: Add do yeet expressions to allow experimentation in nightly #96376
• Final comment period (FCP)
• Stabilization PR

Unresolved Questions

• The name, of course.