A clearer title would be “Countering Qt string bloat” since these are nonstandard string types and these optimizations don’t apply to std::string. Unless someone was using std::wstring for some reason, but I’ve never seen a single use of that class in the wild in my 30 years with C++!
The runtime impact is harder to measure, as this drowns in the noise here. Less code to run and less data to load certainly doesn’t hurt though.
That’s a dangerous assumption. Any library you use now may end up translating the strings to the other format at runtime. It may not, but… I’ve been there and let’s be careful.
A clearer title would be “Countering Qt string bloat” since these are nonstandard string types and these optimizations don’t apply to std::string. Unless someone was using std::wstring for some reason, but I’ve never seen a single use of that class in the wild in my 30 years with C++!
Have a look at the fish-shell codebase - before the rust rewrite finishes, of course!
That’s a dangerous assumption. Any library you use now may end up translating the strings to the other format at runtime. It may not, but… I’ve been there and let’s be careful.