Figure out how to use `push_unchecked` in more places about staticvec HOT 2 CLOSED

I honestly think it has something to do with the fact that MaybeUninit::write in fact has a return value, which is a mutable reference to whatever you just wrote to it.

The docs state this is for your convenience, although IMO it seems like a somewhat strange API. So it may even be that using regular pointer writes in the troublesome spots turns out to work more efficiently (although IIRC that left me with Miri errors at some point early on, because I guess in some cases it wasn't considered the "same" as using the built-in MaybeUninit::write, although generally it should be.)

I'll experiment with some things when I have a bit more time later on to see if I can arrive at a solution that's both fast and sound.

from staticvec.

I'd say push_unchecked is now basically being used where it makes sense to use it (except for filled_with still, but that seems to be a particularly special case.)

from staticvec.