# \[Pre-RFC\] Fixed-capacity view of Vec

**URL:** <https://internals.rust-lang.org/t/pre-rfc-fixed-capacity-view-of-vec/8413>\
**Category:** libs\
**Created:** [September 16, 2018, 6:53pm UTC](https://internals.rust-lang.org/t/pre-rfc-fixed-capacity-view-of-vec/8413 "2018-09-16T18:53:55Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Shnatsel](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/shnatsel/32/4613_2.png) [@Shnatsel](https://internals.rust-lang.org/u/Shnatsel)\
**Post date:** [September 16, 2018, 7:14pm UTC](https://internals.rust-lang.org/t/pre-rfc-fixed-capacity-view-of-vec/8413/3 "2018-09-16T19:14:58Z")

</div>

More like “How to avoid unsafe code” guidelines. And perhaps clippy warnings.

I do believe a coordinated effort for providing good enough safe abstractions so that unsafe code can be eliminated from most crates is required. I was hoping the [security WG proposal](https://internals.rust-lang.org/t/proposal-security-working-group/8282) would result in something like that, but turns out the term “security” is too broad. So here I am, trying to blaze the trail and lead by example.

---

_[View the full topic](https://internals.rust-lang.org/t/pre-rfc-fixed-capacity-view-of-vec/8413)._