# Some \`yeet\` bikeshedding, just for fun

**URL:** <https://internals.rust-lang.org/t/some-yeet-bikeshedding-just-for-fun/21584>\
**Category:** Uncategorized\
**Created:** [September 24, 2024, 10:53pm UTC](https://internals.rust-lang.org/t/some-yeet-bikeshedding-just-for-fun/21584 "2024-09-24T22:53:26Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![steffahn](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/steffahn/32/13288_2.png) [@steffahn](https://internals.rust-lang.org/u/steffahn)\
**Post date:** [September 24, 2024, 10:53pm UTC](https://internals.rust-lang.org/t/some-yeet-bikeshedding-just-for-fun/21584/1 "2024-09-24T22:53:26Z")

</div>

All replies bikeshedding the name `yeet` are moved here from [Why `yeet` in `try` blocks if `break` is good enough?](https://internals.rust-lang.org/t/why-yeet-in-try-blocks-if-break-is-good-enough) in order not to overwhelm the original topic.

This is not the first time for `yeet` bikeshedding discussions, nor the last time, nor the intended time to bring the bikeshedding any closer to any official conclusions; thus this topic thread is also unlisted so that it wonʼt give off any wrong impressions for its unofficial and just-for-fun nature.

---

<div class="post-metadata">

**Author:** ![steffahn](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/steffahn/32/13288_2.png) [@steffahn](https://internals.rust-lang.org/u/steffahn)\
**Post date:** [September 24, 2024, 10:53pm UTC](https://internals.rust-lang.org/t/some-yeet-bikeshedding-just-for-fun/21584/2 "2024-09-24T22:53:30Z")

</div>

Unlisted on September 24, 2024, 10:53pm UTC



---

<div class="post-metadata">

**Author:** ![Vorpal](https://avatars.discourse-cdn.com/v4/letter/v/aca169/32.png) [@Vorpal](https://internals.rust-lang.org/u/Vorpal)\
**Post date:** [September 17, 2024, 5:51pm UTC](https://internals.rust-lang.org/t/some-yeet-bikeshedding-just-for-fun/21584/3 "2024-09-17T17:51:50Z")

</div>

I like the name yeet. I wouldn't mind seeing that stabilised, it is a fun and a bit unexpected thing. Lightens the mood from the typical grey and boring professionalism. Fits right in with the rust community (which I perceive as more welcoming to individual expressions than most programming languages, both online and at events).

Just think about it, it would never in million years be named "yeet" in ISO C++, or Java. Is Rust brave enough to be different here? 😉

---

<div class="post-metadata">

**Author:** ![scottmcm](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/scottmcm/32/2355_2.png) [@scottmcm](https://internals.rust-lang.org/u/scottmcm)\
**Post date:** [September 17, 2024, 6:04pm UTC](https://internals.rust-lang.org/t/some-yeet-bikeshedding-just-for-fun/21584/4 "2024-09-17T18:04:19Z")

</div>

> [@Vorpal](#):
>
> Is Rust brave enough to be different here? 😉

I recommend this old post from niko:

> [@Bikeshed: Rename \`catch\` blocks to \`fallible\` blocks](https://internals.rust-lang.org/t/bikeshed-rename-catch-blocks-to-fallible-blocks/7121/4):
>
> This is how I see it too. Let me expand a bit. I think that there is a belief -- one that I have shared from time to time -- that it is not helpful to use familiar keywords unless the semantics are a perfect match, the concern being that they will setup an intuition that will lead people astray. I think that is a danger, but it works both ways: those intuitions also help people to understand, particularly in the early days. So it's a question of "how far along will you get before the difference…

If this was a fundamentally-new thing, then `yeet` might actually work. But I don't think it's different _enough_ from things in other languages to be worth using a word different from what's already in people's heads anyway.

---

<div class="post-metadata">

**Author:** ![Vorpal](https://avatars.discourse-cdn.com/v4/letter/v/aca169/32.png) [@Vorpal](https://internals.rust-lang.org/u/Vorpal)\
**Post date:** [September 17, 2024, 6:41pm UTC](https://internals.rust-lang.org/t/some-yeet-bikeshedding-just-for-fun/21584/5 "2024-09-17T18:41:16Z")

</div>

That is actually a good point. I always have to think when coding C++ and Python which language uses "except" and which uses "catch". Both are features i use somewhat rarely in both of those languages (even more so in C++, in Python it is hard to avoid dealing with exceptions).

---

<div class="post-metadata">

**Author:** ![binarycat](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/binarycat/32/12210_2.png) [@binarycat](https://internals.rust-lang.org/u/binarycat)\
**Post date:** [September 18, 2024, 7:34pm UTC](https://internals.rust-lang.org/t/some-yeet-bikeshedding-just-for-fun/21584/6 "2024-09-18T19:34:20Z")

</div>

i think it would be needlessly confusing to stabilize yeet\_expr under the name `throw`, as they are different things. the rust equivelent to throwing an exception is `panic`, and this is reflected in `catch_unwind`. `throw` implies nonlocal control flow, which `yeet` is not.

`bail` would be a decent name.

---

<div class="post-metadata">

**Author:** ![Mokuz](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/mokuz/32/7225_2.png) [@Mokuz](https://internals.rust-lang.org/u/Mokuz)\
**Post date:** [September 18, 2024, 10:38pm UTC](https://internals.rust-lang.org/t/some-yeet-bikeshedding-just-for-fun/21584/7 "2024-09-18T22:38:26Z")

</div>

The main issue with `bail` is that it is already used in a lot of error handling crates and so making it a new keyword would be disruptive.

Despite being 'unserious' `yeet` is suprisingly good choise as it is not commonly used as an identifier and has no prior connections to exeptions.

---

<div class="post-metadata">

**Author:** ![josh](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/josh/32/5934_2.png) [@josh](https://internals.rust-lang.org/u/josh)\
**Post date:** [September 18, 2024, 10:50pm UTC](https://internals.rust-lang.org/t/some-yeet-bikeshedding-just-for-fun/21584/8 "2024-09-18T22:50:08Z")

</div>

> [@Mokuz](#):
>
> The main issue with `bail` is that it is already used in a lot of error handling crates and so making it a new keyword would be disruptive.

So was `try`. One pattern we've been observing sometimes is that the crate ecosystem prototypes some great ideas, and they're successful enough that we want to put them in the language or standard library, and then we have the problem of either breaking those popular crates or using a less familiar or less ideal name for the concept.

Worst case, we have editions, and could introduce `bail` over an edition.

---

<div class="post-metadata">

**Author:** ![scottmcm](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/scottmcm/32/2355_2.png) [@scottmcm](https://internals.rust-lang.org/u/scottmcm)\
**Post date:** [September 18, 2024, 10:53pm UTC](https://internals.rust-lang.org/t/some-yeet-bikeshedding-just-for-fun/21584/9 "2024-09-18T22:53:19Z")

</div>

> [@binarycat](#):
>
> the rust equivelent to throwing an exception is `panic`

That's true from an _implementation_ perspective, but I don't think that's the best criterion.

From a "what am I trying to do?" perspective, if in Python you'd `raise InsufficientFundsError`, the rust equivalent is _not_ to `panic_any(InsufficientFundsError)`, but to `throw InsufficientFundsError`.

---

<div class="post-metadata">

**Author:** ![CAD97](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/cad97/32/3460_2.png) [@CAD97](https://internals.rust-lang.org/u/CAD97)\
**Post date:** [September 19, 2024, 12:37am UTC](https://internals.rust-lang.org/t/some-yeet-bikeshedding-just-for-fun/21584/10 "2024-09-19T00:37:58Z")

</div>

> [@Mokuz](#):
>
> Despite being 'unserious' `yeet` is surprisingly good choice as it is not commonly used as an identifier

FWIW I've been using a `yeet!` macro in some projects, expanding to `return Err($e)?`. In the projects large enough to justify it and my `oops!` helper macro, it has been very convenient to use.

Since I find it interesting and tangentially meaningful, YEET# [will be allowed in international Scrabble tournaments](https://www.thebookseller.com/news/collins-adds-2000-new-words-to-official-scrabble-dictionary)\[1\] starting in 2025.

* * *

1. International Scrabble uses the [Collins word list](https://en.wikipedia.org/wiki/Collins_Scrabble_Words), and `#` notates that a word is CSW exclusive; North American tournaments use the smaller [NASPA word list (NWL)](https://en.wikipedia.org/wiki/NASPA_Word_List).

---

<div class="post-metadata">

**Author:** ![lordan](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/lordan/32/2107_2.png) [@lordan](https://internals.rust-lang.org/u/lordan)\
**Post date:** [September 19, 2024, 2:35pm UTC](https://internals.rust-lang.org/t/some-yeet-bikeshedding-just-for-fun/21584/11 "2024-09-19T14:35:28Z")

</div>

> [@scottmcm](#):
>
> From a "what am I trying to do?" perspective, if in Python you'd `raise InsufficientFundsError`, the rust equivalent is _not_ to `panic_any(InsufficientFundsError)`, but to `throw InsufficientFundsError`.

I'd argue that is not a direct equivalent. Like @binarycat, to me `throw` reads "nonlocal exception", that will be caught and handled anywhere up the call stack, whereas in Rust it will always only go to the immediate surrounding `try` or function block, and no further.

Since we are already bikeshedding, my vote would be for `error` (or even just `err` if we are lazy in typing), since `Err` results is what we are constructing:

```rust
let Ok(val) = validate(expression) else {
    error format!("{expression:?} is invalid!"); 
}

```

Not to mention it'd give me fuzzy, warm, nostalgic BASIC vibes 🙂

---

<div class="post-metadata">

**Author:** ![PatchMixolydic](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/patchmixolydic/32/7651_2.png) [@PatchMixolydic](https://internals.rust-lang.org/u/PatchMixolydic)\
**Post date:** [September 24, 2024, 4:45pm UTC](https://internals.rust-lang.org/t/some-yeet-bikeshedding-just-for-fun/21584/12 "2024-09-24T16:45:09Z")

</div>

Actually using `yeet` as the keyword would come across as an extremely-ill advised attempt to appeal to ~~young people~~ the _iPod generation_ using the hip and trendy memes of ereyesteryear. If `yeet` is ever seriously considered for stabilization, I'd like to counterpropose [`weorpan`](https://en.wiktionary.org/wiki/weorpan#Old_English), which is equally unused as an identifier and equally up-to-date with current language trends.

---

<div class="post-metadata">

**Author:** ![CAD97](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/cad97/32/3460_2.png) [@CAD97](https://internals.rust-lang.org/u/CAD97)\
**Post date:** [September 24, 2024, 8:43pm UTC](https://internals.rust-lang.org/t/some-yeet-bikeshedding-just-for-fun/21584/13 "2024-09-24T20:43:03Z")

</div>

> [@PatchMixolydic](#):
>
> [_Weorpan_ is] equally up-to-date with current language trends [as _yeet_].

This is probably false. While usage is certainly way down from peak meme, as a vague indicator, Google Trends shows _yeet_ as being stable around 20% of its peak, nothing for _weorpan_, and _yoink_ (what I believe more people would recognize as being a "legitimate" word, picked for being the best antonym of _yeet_ IMHO) with a nonzero search interest that's no more than around 3% of _yeet_'s.

* * *

Anyway, the use of yeet in the unstable syntax was to use a silly option with low likelihood of being the real choice, just to have _something_ agreed on to be able to discuss the feature without going through endless bikeshed up front. I do agree it's a _possible_ choice, but unless the purpose of a thread is to discuss the choice of syntax specifically, the use of `yeet` or `☃` or whatever should be understood as "placeholder for an appropriate keyword," not as an actual choice, until otherwise stated.

And yeah, inertia of being used on unstable (behind a `do` prefix) does lend some legitimacy to the choice that might not otherwise exist. But Rust's design isn't a popularity contest (nor a democracy nor republic), and the teams involved have the stated position that `yeet` is indeed just a placeholder, and syntax will be relitigated before stabilization (bare minimum FCP).

---

<div class="post-metadata">

**Author:** ![Vorpal](https://avatars.discourse-cdn.com/v4/letter/v/aca169/32.png) [@Vorpal](https://internals.rust-lang.org/u/Vorpal)\
**Post date:** [September 24, 2024, 9:17pm UTC](https://internals.rust-lang.org/t/some-yeet-bikeshedding-just-for-fun/21584/14 "2024-09-24T21:17:31Z")

</div>

I kind of want to learn how to write proc macros now.

So I could make a Ye Olde Ruſt novelty transformation pass. Never had the motivation before to learn proc macros.

---

<div class="post-metadata">

**Author:** ![steffahn](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/steffahn/32/13288_2.png) [@steffahn](https://internals.rust-lang.org/u/steffahn)\
**Post date:** [March 18, 2026, 9:17pm UTC](https://internals.rust-lang.org/t/some-yeet-bikeshedding-just-for-fun/21584/15 "2026-03-18T21:17:55Z")

</div>

Closed on March 18, 2026, 9:17pm UTC

This topic was automatically closed 540 days after the last reply. New replies are no longer allowed.
