The libmongodbcapi contains a whole bunch of unfortunate coding constructs such as

} catch (const std::exception&) {
    last_error = LIBMONGODB_CAPI_ERROR_UNKNOWN;
    return nullptr;
}

This paradigm of coding, coupled with the prevalent use of uasserts in the client/embedded/ codebase, results in a frustrating (and time consuming) debugging experience for anyone who happens to have a patch build fail a test in this area. Could we add better exception handling in this library?