Also, unfortunately, https://github.com/boostorg/geometry/issues/566 is still present in the RC. Barend assured me the fix was already in Beta1; seeing as there are no notes for Boost.Geometry in the release, I’m wondering if the release process is actually skipping some portions of the codebase on purpose...

El 7 abr. 2019, a la(s) 07:07, Rainer Deyke via Boost-users <boost-users@lists.boost.org> escribió:

On 07.04.19 14:13, Marshall Clow via Boost-users wrote:
On Sat, Apr 6, 2019 at 10:53 AM Rainer Deyke via Boost-users <
boost-users@lists.boost.org> wrote:
On 04.04.19 16:27, Marshall Clow via Boost-users wrote:
As always, the release managers would appreciate it if you download
the candidate of your choice and give building it a try. Please report
both success and failure, and anything else that is noteworthy.

boost::movelib::adaptive_merge continues to be broken if
iterator_traits<RandIt>::size_type != std::size_t.  This breaks
boost::container::flat_map when cross-compiling for MacOS.  I have
previously reported this error here.

I consider this a critical error - as in, I won't be able to upgrade to
Boost 1.70 at all unless this error is fixed for the release.

This is https://github.com/boostorg/move/issues/25, correct?

Yes.


--
Rainer Deyke (rainerd@eldwood.com)

_______________________________________________
Boost-users mailing list
Boost-users@lists.boost.org
https://lists.boost.org/mailman/listinfo.cgi/boost-users