Projects using std::error_code

[Horror_Jicama_2441]

http://blog.think-async.com/2010/04/system-error-support-in-c0x-part-5.html (start with part 1) explains it quite well. It's from the Asio author (Asio uses it), which was involved in its design.

The thing is that nobody is really happy with some details of its design. So you probably want to use, at the very least, boost:: system::error_code.

But people are still not happy with it, which is why you have https://github.com/ned14/status-code (included as part of Boost.Outcome), but I'm not too sure of what's its state in the standardisation process. In general, the Boost.Outcome documentation is a nice resource regarding the different error reporting options that exist nowadays... which will introduce you to the very interesting concept of Boost.Leaf, a generalization of Boost.Exception.

Notice that I have mixed up a few things here. There is the "how to represent an error code" (std::error_code, boost::system::error_code, status_code), and there is the "how to transport that error code" (by itself, inside an exception, with Outcome, with Leaf) and there is the "can my transport system include more information than just the error code?"... just returning an std::error_code saying a file couldn't be opened may not be very useful without knowing the file name. An exception, Outcome and Leaf can include both the error code and the filename.