Peter Dimov
Peter Dimov
We seem to be missing a macro for the C++11 header ``.
ContainerHash now has generic support for ranges, contiguous ranges and unordered ranges, so `boost::hash` should work for the containers as-is, without the need for library-provided `hash_value` overloads. I don't see...
https://github.com/boostorg/context/blob/fb0f3eab4d14ce2de4cf3a5446c8a0f735a9282d/include/boost/context/detail/config.hpp#L33-L35 defines `BOOST_USE_UCONTEXT` on Cygwin. This causes Fiber to fail to build, because it tries to use ucontext, but Context is built with fcontext. If Context is built with ucontext...
Unfortunately the argument order is incorrect, so perhaps add `tuple_for_each_` with the correct one and make it variadic.
``` template auto list_invoke( F&& f ); // Returns: f( T{}... ), where T... are the elements of L, or mp_value{}..., for a value list ``` Motivation: https://twitter.com/ericniebler/status/1671986987396415491 `list_invoke( [&](auto......
The Boost convention is that `cmake --build .` only builds the libraries. Test libraries and executables are built with `cmake --build . --target tests`.
I don't see it in https://www.boost.org/doc/libs/1_85_0/libs/static_string/doc/html/static_string/ref/boost__static_strings__basic_static_string.html.
`constexpr boost::static_strings::basic_static_string s( "name" );` fails to compile (under C++20): https://godbolt.org/z/fvPs3rxa7 Background: in order to write functions that take strings as template arguments, as in `function()`, one needs to declare...
The Boost convention is that `cmake --build .` only builds the libraries. Test libraries and executables are built with `cmake --build . --target tests`.
The Boost convention is that `cmake --build .` only builds the libraries. Test libraries and executables are built with `cmake --build . --target tests`.