Closed basiliscos closed 3 years ago
if it was fixed, why it still appears in boost v.1.75 and gcc 10.2?
It's looking like for --std
before 20, one of the GCC 10 series appears to have changed from wanting the legacy concepts syntax to wanting the new concepts syntax. I've had bug reports complaining that GCC 10 didn't work without the logic it currently is, now I have your bug report saying that GCC 10 doesn't work with the current logic.
What we might try is what Chris K does here: https://github.com/chriskohlhoff/asio/blob/master/asio/include/asio/detail/config.hpp#L422. What do you think?
Looks better than nothing, if the warnings can be silenced. Will be perfect, if this can be done automatically. )
Should be fixed now, if the new logic holds. You can check it for yourself at https://github.com/boostorg/outcome/commits/develop. Thanks for the BR!
Hi there. Here is a warning which i get using gcc
v10.2.1
:Can it be silenced? Is there any hope, that it will be fixed on the next boost release?