The views are not for this indeed. But if you're not allocating your buffer most likely comes from a `heapless::Vec` somewhere, and you can get a view pointing to it rather easily, so instead of allocating a `[MaybeUninit<T>; N]` you'd directly allocate a `Vec<T, N>`. But yes this is a bit less flexible.

The storage abstraction can probably also abstract over a `&mut [MaybeUninit<T>]`.
But that would be less pratctical that the `View` API overall, since you'd loose the ability to convert between the different versions of the `Vec`:

- `Vec<T, const N: usize>` is essentially `VecInner<[MaybeUninit<T>; N]>`
- `VecView<T>` is essentially `VecInner<[MaybeUninit<T>]>`
- `VecSlice<'buffer, T>` would be `VecInner<&' mut [MaybeUninit<T>]>`.
This would work, but you would not be able to obtain a `VecSlice` from an existing `Vec`.

There are also some niceties that you wouldn't have (especially re-borrowing).