Re:Small Strings in Rust: smolstr vs. smartstring
by tomcam on Sunday August 25, 2024 @12:17AM
(#41344348)
Oh! So the string itself is still on the heap? I assumed it was all on the stack.
Re:Small Strings in Rust: smolstr vs. smartstring
by super_flanker on Sunday August 25, 2024 @12:48AM
(#41344467)
No, let me try to explain differently. If `compact_str` was not used, then your normal `String` would take 24 bytes of stack space (regardless of the string size) + heap space. What `compact_str` is trying to do is not use heap when string content is less than 24.
Re:Small Strings in Rust: smolstr vs. smartstring
by tomcam on Sunday August 25, 2024 @01:45AM
(#41344724)
Thank you. That aligns with what I originally thought.
Re:Small Strings in Rust: smolstr vs. smartstring
by Dylan16807 on Sunday August 25, 2024 @09:18AM
(#41347089)
> It's quite possible to make the small string buffer larger, but that comes at the cost of the large string representation taking up more space than necessary on the stack. IIRC libstdc++ does this, which makes its std::string take up 32 bytes on the stack.
Though to follow through on that, 24 bytes is also more than necessary. You don't have to be very clever to shrink your string size to 16 bytes (6 for the pointer, 6 for the size, 4 to store either capacity or spare capacity as floating point).
It's quite possible to make the small string buffer larger, but that comes at the cost of the large string representation taking up more space than necessary on the stack. IIRC libstdc++ does this, which makes its std::string take up 32 bytes on the stack.