6 comments

[ 3.2 ms ] story [ 23.1 ms ] thread
Documentation isn't very clear about what's actually provided by the libraries (if you dig you can eventually find it).

Looks at first glance more comprehensive than the Intel TBB.

> if you dig you can eventually find it

You can? I looked all over the site, and I couldn't find it (other than going to GitHub and reading the source code).

Users need to be cautious about this:

> Although Google is part of the minority of the C++ community that doesn’t use exceptions, we recognize that it is a minority and believe that code is often better when it’s exception-safe. We’ve done our best to make things exception-safe. However, we won’t contort things to support all possible exceptions — if you have a hash functor or operator== that throws, we may just mark it noexcept instead.

I'm as gung-ho as it gets on C++ exceptions and even I think it's reasonable for a library to require that operator== and hash functors not throw.