# Pre-RFC: flexible \`try fn\`

**URL:** <https://internals.rust-lang.org/t/pre-rfc-flexible-try-fn/7564>\
**Category:** Uncategorized\
**Created:** [May 17, 2018, 11:49pm UTC](https://internals.rust-lang.org/t/pre-rfc-flexible-try-fn/7564 "2018-05-17T23:49:27Z")\
**Posts on this page:** 1\
**Showing post:** 144

<div class="post-metadata">

**Author:** ![aturon](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/aturon/32/3272_2.png) [@aturon](https://internals.rust-lang.org/u/aturon)\
**Post date:** [May 21, 2018, 5:31pm UTC](https://internals.rust-lang.org/t/pre-rfc-flexible-try-fn/7564/144 "2018-05-21T17:31:29Z")

</div>

> [@rvolgers](#):
>
> My point was that languages without a BDFL might have to provide other means for this, such as a trusted committee that takes this role.

Just to clarify: Rust's evolution is ultimately governed by a set of formal [teams](http://rust-lang.org/team.html) covering various areas of development. The Language Design team ultimately makes decisions on language-related RFCs, and works closely together (and in consultation with the broader community) to ensure an overall coherent vision of where to take the language.

---

_[View the full topic](https://internals.rust-lang.org/t/pre-rfc-flexible-try-fn/7564)._