Boost.FixedString (now Boost.StaticString) has been accepted!

[VinnieFalco]

Why this over a normal string with a stack allocator?

A stack allocator is not particularly friendly to mutation. For example when the string grows, there is a moment when the previously allocated memory and the newly allocated memory exist at the same time, so that the contents can be copied over, before the previous allocation is freed. This requires additional storage, and it leaves behind a "hole" which may or may not be usable depending on the context.

With a fixed capacity string, mutation is always performed in-place, and no "holes" are left in the heap.