# Bikeshed: Rename \`catch\` blocks to \`fallible\` blocks

**URL:** <https://internals.rust-lang.org/t/bikeshed-rename-catch-blocks-to-fallible-blocks/7121>\
**Category:** language design\
**Created:** [March 23, 2018, 6:09am UTC](https://internals.rust-lang.org/t/bikeshed-rename-catch-blocks-to-fallible-blocks/7121 "2018-03-23T06:09:25Z")\
**Posts on this page:** 1\
**Showing post:** 49

<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:** [April 3, 2018, 10:29am UTC](https://internals.rust-lang.org/t/bikeshed-rename-catch-blocks-to-fallible-blocks/7121/49 "2018-04-03T10:29:12Z")

</div>

I’ve searched StackOverflow for “`[rust] try`”. There weren’t many questions/answers that mention it. I’ve edited a few to remove irrelevant `try!`. The ones left are mainly duplicates of a question about use of `try!` and `?` in `main()` (which is being [fixed](https://github.com/rust-lang/rust/issues/43301)).

The second edition of the Rust book and current Rust by Example have already removed all mentions of `try!`.

It’s possible to make rustfix or rustfmt replace `try!` with `?` automatically.

So overall I think it’s feasible to reduce the `try!` macro to a historical curiosity to the point it won’t be actively confusing to newbies coming to Rust.

---

_[View the full topic](https://internals.rust-lang.org/t/bikeshed-rename-catch-blocks-to-fallible-blocks/7121)._