3 ms·
I agree with most points, but "std:string was designed 25+ years ago, over a dozen CPU generations ago; the demands of today are must different." Sure, but yo
by raverbashing 12y ago
I agree with most points, but
"std:string was designed 25+ years ago, over a dozen CPU generations ago; the demands of today are must different."
Sure, but you don't need to break the API for that
You can replace the allocator in a C program without changing malloc/free to something else, this might have been a design goal. This way you can go back and forth to it, run your tests again, compare performance again, etc