mastodon 4.7.3I'm a programmer who loves Rust. I'm a dancer and play traditional Irish music. I'm an "urbanist" and love bicycles and public transit. I enjoy woodworking and machining and I'm learning to make Irish flutes and pennywhistles.
I find that in #rustlang and elsewhere I sometimes really need a one-or-more representation (rather than zero-or-more). There are a number of crates that provide non-empty collections for this, but I've always found one thing or another missing.
There's still a lot to do (including API documentation), but I think I'm happy with the overall shape of my crate: Mitsein. AFAICT, it's one of the most comprehensive crates that attempts to tackle this problem. Feedback, issues, and PRs are welcome!
@blp I believe this mostly comes down to variance and drop checking. Rust infers variance and "dropck" based on the usage of T in data structures. This doesn't apply to fns, since they cannot interact with or "store" T directly but only via parameters.