# Fortifying the process against feature bloat

**URL:** <https://internals.rust-lang.org/t/fortifying-the-process-against-feature-bloat/7608>\
**Category:** policy\
**Created:** [May 21, 2018, 7:51pm UTC](https://internals.rust-lang.org/t/fortifying-the-process-against-feature-bloat/7608 "2018-05-21T19:51:40Z")\
**Posts on this page:** 1\
**Showing post:** 24

<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:** [May 23, 2018, 6:29pm UTC](https://internals.rust-lang.org/t/fortifying-the-process-against-feature-bloat/7608/24 "2018-05-23T18:29:16Z")

</div>

> [@Centril](#):
>
> A closed RFC means that the same idea shouldn’t be filed again. It’s up to the team to judge what “same” constitutes

To elaborate on this, I think it could be, among other things,

- New motivation is found for the same feature
- An alternative solution is found for the same problem
- Over a substantial time period, the issue it addresses has become serious (probably at least a year, increasing as we get further from 1.0)

---

_[View the full topic](https://internals.rust-lang.org/t/fortifying-the-process-against-feature-bloat/7608)._