Use std::system_category().message(err), which internally dispatches to strerror_r/s, and should handle unknown errors.
See: https://github.com/llvm/llvm-project/blob/4e9e83400a5702059c8a18e2fb6174038875e8a6/libcxx/src/system_error.cpp#L231-L237 for one standard library implementation.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline and AI policy for information on the review process. A summary of reviews will appear here.
<!--5faf32d7da4f0f540f40219e4f7537a3-->
6 | @@ -7,9 +7,8 @@ 7 | 8 | #include <string> 9 | 10 | -/** Return system error string from errno value. Use this instead of 11 | - * std::strerror, which is not thread-safe. For network errors use 12 | - * NetworkErrorString from sock.h instead. 13 | +/** Return system error string from errno value. For network errors 14 | + * use NetworkErrorString from sock.h instead.
/// Return system error string from errno value. For network errors
/// use NetworkErrorString from sock.h instead.
nit: The different indent looks a bit ugly? Could use a fixed-size doxygen comment?
Sure, changed.
Dropped any Windows-specific changes here.
Use std::system_category().message(err), which internally dispatches to
strerror_r/s, and should handle unknown errors.
See: https://github.com/llvm/llvm-project/blob/4e9e83400a5702059c8a18e2fb6174038875e8a6/libcxx/src/system_error.cpp#L231
22 | - /* Too bad there are three incompatible implementations of the 23 | - * thread-safe strerror. */ 24 | - const char *s = nullptr; 25 | -#ifdef WIN32 26 | - if (strerror_s(buf, sizeof(buf), err) == 0) s = buf; 27 | -#else
Is it safe to remove this Windows-specific code?