Re: Boost.Compute broken in 1.86.0 because of UUID changes, 1.86.1?

From: John Maddock (jz.maddock_at_[hidden])
Date: 2024-08-22 09:41:03

On 22/08/2024 09:55, Boris Kolpackov via Boost wrote:
> Peter Dimov via Boost <boost_at_[hidden]> writes:
>
>> Because Boost.Compute (boost/compute/detail/sha1.hpp) uses an
>> implementation detail of Boost.UUID (boost/uuid/detail/sha1.hpp),
>> and because I changed the implementation to fix an endianness
>> issue, <boost/compute.hpp> now causes a compile error in 1.86.0
> Any sense why this was not detected (e.g., by CI) when the change
> was made or during pre-release testing? It seems to me compiling
> any translation unit that included <boost/compute.hpp> would have
> picked this up, no?

Yes, but compute's CI would not have been triggered just because a 
dependency changed, and it has no active maintainer either.

John.