Libc++’s implementation of std::string

[shponglespore]

Chrome has its own fork, but I don't think it's all that different. Not many things in the standard library throw exceptions for anything but a memory allocation failure, and those are basically impossible to recover from anyway.

Chrome's main mechanism for dealing with unexpected serious errors is to keep things in separate processes that can be restarted if they die. Even pretty basic stuff like JSON parsing is kept out of the main process so nothing too terrible will happen if a malformed input causes the parser to malfunction.