itertools VS staticvec

It might be a good fit for Itertools

Some relevant discussion: https://github.com/rust-itertools/itertools/pull/531

It's un-deprecated because try_fold is considered to be not as ergonomic for now.

This crate of mine for example is currently literally unusable until the deeply fundamental features that John Random kinda-sorta removed in this pull request, ostensibly in preparation for whatever shittily stated syntax is ultimately establihed by whatever the hell "keyword generics" actually is (I really don't know, like this isn't a joke, I fundamentally do not understand what the fuck they're proposing at all in any way or how it's meaningfully and usefullly different from the previous syntax).

If you're on nightly, I have a crate that I'd say would seem to be exactly what you're looking for.

I'd say the module system can sometimes get in the way of even the most technically well-documented crate out there. It's why for example I carefully rexport the various types implemented by my crate StaticVec from lib.rs such that the main docs page looks like this, even though "under the hood" everything is actually about as modular as you might expect it to be.

Here.

Your link there is rather outdated. mem::unitialized() is deprecated and not recommended for use. MaybeUninit works more than fine in my experience, anyways.

The lack of decltype-esque functionality has consequences that are far-reaching enough to be worthy of more than a throwaway mention, IMO. See this ongoing issue for a crate of mine, for example.

If you're on nightly, my crate StaticVec definitely has your use case covered and then some.

Looks like this crate uses the full const_generics instead of min_const_generics (see here), along with a couple dozen other unstable features. I'm not sure how much of that could easily be removed, since it is often the tendency to enable tons of unstable features when you are already on nightly because of something like const generics.