> Beats the heck out of taking an unexpected GC call somewhere later when you weren't expeccting it. How is that an issue with c++ `std::string`
Definitely, and where `std::string`'s interface is not enough, use thrid party libs which work on std::strings, like boost string algoriths, std regex, or uftcpp.
No that's BS. `std::string` should be used where ever it is applicable. The whole issue that this post about chrome was talking about was dealing with a poor usage of `std::string`, such as passing c_str() to then go…
Copy on write is not at all helpful in a language like C++ where concurrency can be concerned.
Yeah, I can't believe this crap has become de-facto web design.
I used it for testing Spare Matrix kernels I wrote for my Uni thesis. However, god knows why this site is considered news worthy. I mean it's the same as it was yesterday, and the day before...
> Beats the heck out of taking an unexpected GC call somewhere later when you weren't expeccting it. How is that an issue with c++ `std::string`
Definitely, and where `std::string`'s interface is not enough, use thrid party libs which work on std::strings, like boost string algoriths, std regex, or uftcpp.
No that's BS. `std::string` should be used where ever it is applicable. The whole issue that this post about chrome was talking about was dealing with a poor usage of `std::string`, such as passing c_str() to then go…
Copy on write is not at all helpful in a language like C++ where concurrency can be concerned.
Yeah, I can't believe this crap has become de-facto web design.
I used it for testing Spare Matrix kernels I wrote for my Uni thesis. However, god knows why this site is considered news worthy. I mean it's the same as it was yesterday, and the day before...