# Labeled Returns?

**URL:** <https://internals.rust-lang.org/t/labeled-returns/9371>\
**Category:** Uncategorized\
**Created:** [February 5, 2019, 8:25pm UTC](https://internals.rust-lang.org/t/labeled-returns/9371 "2019-02-05T20:25:53Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![kornel](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/kornel/32/2711_2.png) [@kornel](https://internals.rust-lang.org/u/kornel)\
**Post date:** [February 5, 2019, 11:40pm UTC](https://internals.rust-lang.org/t/labeled-returns/9371/3 "2019-02-05T23:40:54Z")

</div>

Variants of this (e.g. `break ok`, `fail err`, [`reta`](https://internals.rust-lang.org/t/pre-rfc-catching-functions/6505/69)) [have already been proposed](https://internals.rust-lang.org/t/pre-rfc-flexible-try-fn/7564). In that thread it seems like there are mixed feelings about such extensions.

So if you’re proposing a similar thing, it’d be worthwhile to address concerns already raised (how does it work with `async` wrapping? Does it work with `try` blocks? Does it work with the `Try` trait?), what new your proposal brings, and why this variant is better than others.

---

_[View the full topic](https://internals.rust-lang.org/t/labeled-returns/9371)._
