Vladislav Shchapov

@KFilipek In any way, the initialization of an ``std::atomic`` variable is not atomic (https://en.cppreference.com/w/cpp/atomic/atomic/atomic) and because of this, there may be errors. It's best solution to use ``std::atomic_ref`` and zero-initialized...

> IMHO in C++ 11 it is perfectly valid code, as in C++11 constructor of `std::atomic` is intentionally made trivial to allow correct (zero) initialization of global atomics. Maybe not:...

PR updated.

Rebased and ping.

GCC and clang TSAN does not support atomic_thread_fence: - https://stackoverflow.com/questions/70542993/why-does-the-thread-sanitizer-complain-about-acquire-release-thread-fences - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97868 - https://github.com/google/sanitizers/issues/1352

I think this is a very bad idea. Also, Boost is required by Asio for C++03 only.

> And my new libraries Boost.Http.Proto and Boost.Http.IO which work with Boost.Asio, Boost.URL, and Boost.JSON. Plus theres Boost.MySQL and soon even Boost.Redis both using Boost.Asio. > > These don't work...

@vinniefalco > the rest of all the wonderful Boost libraries which are actively maintained I'm sorry, but... "rest wonderful" or really "rest in peace"? For example. Very interesting libraries Boost...

@vinniefalco > It is that users prefer to only use libraries that have no other dependencies. No! No! Dependencies should be benefit, not the size of the executable. Prior to...

@grisumbras > But having 10 unmaintained copies of Boost.Config, Boost.Core, Boost.Align and whatever else is not bloat, because they are not explicit dependencies In C++11/C++14 era, most of these libraries...