Peter Dimov

Results 289 comments of Peter Dimov

boost 1.78.0 (and many previous versions?) do not support the documented GCC versions.. "This library now requires a C++11 or later compiler" should minimal requirements be updated?

I'm not sure what's the relevance of GCC 5.2? It's a minor version (a patch release), and GCC 5 is up to 5.5 now I think? Note that the version...

boost 1.78.0 (and many previous versions?) do not support the documented GCC versions.. "This library now requires a C++11 or later compiler" should minimal requirements be updated?

Since the default for GCC 6 is C++14, there's not much point in keeping the library C++11 if you don't support GCC 5.

boost 1.78.0 (and many previous versions?) do not support the documented GCC versions.. "This library now requires a C++11 or later compiler" should minimal requirements be updated?

Yes, I think the reason we're in this thread is that the Boost release notes (what it says on the tin) do not correspond to the actual content. It would...

boost 1.78.0 (and many previous versions?) do not support the documented GCC versions.. "This library now requires a C++11 or later compiler" should minimal requirements be updated?

I'm not sure Optional has something to do with this error, even if the include chain points to it because it happened to include `boost/type_traits/is_default_constructible.hpp`. The instantiation point is actually...

Master list of macro and symbol collision issue reports in all Boost libraries

The motivation for consistently applying a BOOST_ prefix even to unique include guards is that companies want to prepare private Boost releases (that can coexist with the official one, or...

CMakeLists.txt appears to have far too many dependencies

https://pdimov.github.io/boostdep-report/develop/test.html#mpl

`BOOST_TEST(p1 == p2)` doesn't always test `p1 == p2`

This behavior could be pretty surprising when one does e.g. `BOOST_TEST(x.begin() == x.end());` and the iterators happen to be pointers to char (as they are for `boost::string_view` for example, or...

Fix to add wolfSSL configure support in ASIO

No, sorry. Only Chris can do that.

Add CMakeLists.txt

The CMakeLists.txt is automatically generated by `boostdep --cmake numeric/ublas`; `boostdep` takes the requirement from your `meta/libraries.json`. I would recommend leaving it as-is, because (a) C++20 is too high a requirement...

Add CMakeLists.txt

Unrelated to this PR, but are you aware that Boost releases are done from the `master` branch, and you haven't touched it since 2019? That is, none of the changes...