5 Dec
2019
5 Dec
'19
9:52 p.m.
On 6/12/2019 03:11, Vinnie Falco wrote:
When dealing primarily with text based protocols: HTTP, URL, JSON, etc... you usually want to perform string operations. I agree that "drop-in replacement for std::string" is not a precise description for the purpose of the library, but it is partially correct. If you have code that currently uses std::string to perform calculations, and you want to impose a limit on the amount of data it can process while simultaneously avoiding memory allocations, a fixed_string is going to be easier to integrate than vector<char>.
vector and/or static_vector combined with Boost.StringAlgorithm? Maybe we should just be making a more modern static_vector rather than a fixed_string.