# Grammatical ambiguity around \`catch\` blocks

**URL:** <https://internals.rust-lang.org/t/grammatical-ambiguity-around-catch-blocks/4807>\
**Category:** language design\
**Created:** [February 17, 2017, 8:56pm UTC](https://internals.rust-lang.org/t/grammatical-ambiguity-around-catch-blocks/4807 "2017-02-17T20:56:51Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![Ixrec](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/ixrec/32/6754_2.png) [@Ixrec](https://internals.rust-lang.org/u/Ixrec)\
**Post date:** [April 3, 2017, 10:22pm UTC](https://internals.rust-lang.org/t/grammatical-ambiguity-around-catch-blocks/4807/16 "2017-04-03T22:22:26Z")

</div>

Probably worth linking to [[pre-rfc] Stable features for breaking changes](https://internals.rust-lang.org/t/pre-rfc-stable-features-for-breaking-changes/5002) at this point since a good chunk of that thread has been discussing the idea of “epochs” as a way of introducing minor breaking changes such as making catch a keyword, and the details of that idea seem to fit the spirit of your post.

---

_[View the full topic](https://internals.rust-lang.org/t/grammatical-ambiguity-around-catch-blocks/4807)._