@jeremy.laumon.name Nice, from a quick look (e.g. Span, Vector) it's using int instead of size_t for operator[] and lengths.

Curious if that's to avoid unsigned types (unless working with bit-shifting logic), or mainly to save 4 bytes on the struct sizes?

@laurelkeys @jeremy.laumon.name yes, sizes/capacities are 4 bytes to save space and because I'm fairly confident I will never need more that 2 billion items 😄 (and if I do, I'll make a specific thing for that case). Memory block sizes use int64 because I might need to allocate more than 2GB 😉

And both are signed I want to be able to detect underflows and signed integers come with a built-in solution for that 😂