#segment #memory #vec #data-structures #size #chunks #allocate


SegVec data structure for rust. Similar to Vec, but allocates memory in chunks of increasing size

7 releases

0.2.0 Jul 31, 2023
0.1.5 Jan 17, 2022
0.1.3 Jul 7, 2021
0.1.1 Jun 30, 2021

#154 in Memory management

Download history 53/week @ 2023-12-10 63/week @ 2023-12-17 1/week @ 2023-12-31 13/week @ 2024-01-07 24/week @ 2024-01-14 11/week @ 2024-01-21 11/week @ 2024-01-28 6/week @ 2024-02-11 17/week @ 2024-02-18 46/week @ 2024-02-25 52/week @ 2024-03-03 83/week @ 2024-03-10 31/week @ 2024-03-17 41/week @ 2024-03-24

210 downloads per month
Used in 2 crates (via mbroker)

MIT license



docs.rs crates.io

This crate provides the SegVec data structure.

It is similar to Vec, but allocates memory in chunks of increasing size, referred to as "segments". This involves a few trade-offs:


  • Element addresses are stable across push operations even if the SegVec must grow.
  • Resizing only allocates the additional space needed, and doesn't require copying.


  • Operations are slower (some, like insert, remove, and drain, are much slower) for a SegVec than for a Vec (multiple pointer dereferences, mapping indices to (segment, offset) pairs)
  • Direct slicing is unavailable (i.e. no &[T] or &mut [T]), though slice and slice_mut are available

Use Cases

  1. You have a long-lived Vec whose size fluctuates between very large and very small throughout the life of the program.
  2. You have a large append-only Vec and would benefit from stable references to the elements


  • small-vec - Uses SmallVec instead of Vec to store the list of segments, allowing the first few segment headers to live on the stack. Can speed up access for small SegVec values.
  • thin-segments - Uses ThinVec instead of Vec to store the data for each segment, meaning that each segment header takes up the space of a single usize, rathern than 3 when using Vec.

License: MIT