In general, the library returns a StatusOr if an error is possible. Some functions return objects that are not wrapped in a StatusOr<> but will themselves return a StatusOr<> to signal an error. For example, wrappers for asynchronous operations return future<StatusOr<T>>.
Applications should check if the StatusOr<T> contains a value before using it, much like how you might check that a pointer is not null before dereferencing it. Indeed, a StatusOr<T> object can be used like a smart-pointer to T, with the main difference being that when it does not hold a T it will instead hold a Status object with extra information about the error.
You can check that a StatusOr<T> contains a value by calling the .ok() method, or by using operator bool() (like with other smart pointers). If there is no value, you can access the contained Status object using the .status() member. If there is a value, you may access it by dereferencing with operator*() or operator->(). As with all smart pointers, callers must first check that the StatusOr<T> contains a value before dereferencing and accessing the contained value. Alternatively, callers may instead use the .value() member function which is defined to throw a RuntimeStatusError if there is no value.
Example
namespace pubsub_admin = ::google::cloud::pubsub_admin;
[](pubsub_admin::TopicAdminClient client, std::string const& project_id) {
// The actual type of `topic` is
// google::cloud::StatusOr<google::pubsub::v1::Topic>, but
// we expect it'll most often be declared with auto like this.
for (auto& topic : client.ListTopics(project_id)) {
// Use `topic` like a smart pointer; check it before de-referencing
if (!topic) {
// `topic` doesn't contain a value, so `.status()` will contain error
// info
std::cerr << topic.status() << "\n";
break;
}
std::cout << topic->DebugString() << "\n";
}
}
See Also
google::cloud::future for more details on the type returned by asynchronous operations.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[[["\u003cp\u003eThis page provides documentation for error handling in the C++ Pub/Sub library, with versions ranging from 2.11.0 up to the latest release candidate 2.37.0-rc.\u003c/p\u003e\n"],["\u003cp\u003eThe library generally uses \u003ccode\u003eStatusOr<T>\u003c/code\u003e to handle potential errors, where \u003ccode\u003eT\u003c/code\u003e represents a successful return type, allowing for smart-pointer-like behavior in error checking.\u003c/p\u003e\n"],["\u003cp\u003eYou can check for a value within a \u003ccode\u003eStatusOr<T>\u003c/code\u003e object using \u003ccode\u003e.ok()\u003c/code\u003e or \u003ccode\u003eoperator bool()\u003c/code\u003e, and if no value exists, you can access the error \u003ccode\u003eStatus\u003c/code\u003e object via \u003ccode\u003e.status()\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eDereferencing \u003ccode\u003eStatusOr<T>\u003c/code\u003e with \u003ccode\u003eoperator*()\u003c/code\u003e or \u003ccode\u003eoperator->()\u003c/code\u003e provides access to the value, but using \u003ccode\u003e.value()\u003c/code\u003e will throw \u003ccode\u003eRuntimeStatusError\u003c/code\u003e if no value is present or terminate the program if exceptions are disabled.\u003c/p\u003e\n"],["\u003cp\u003eAsynchronous operations will return a \u003ccode\u003efuture<StatusOr<T>>\u003c/code\u003e, allowing you to use error checking in the same fashion as \u003ccode\u003eStatusOr<T>\u003c/code\u003e, and more information is available in \u003ccode\u003egoogle::cloud::future\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,[]]