From: Hans Dembinski (hans.dembinski_at_[hidden])
Date: 2020-12-09 11:07:30
> On 8. Dec 2020, at 15:34, Glen Fernandes <glen.fernandes_at_[hidden]> wrote:
> On Tue, Dec 8, 2020 at 4:53 AM Hans Dembinski <hans.dembinski_at_[hidden]> wrote:
> Was this issue in algorithm::reduce introduced now (i.e. wasn't
> present in 1.74)? If not, since which Boost release has it been
The problem was introduced on Friday Jan 31, 20202, so has been around since Boost-1.73.
>> I cannot decide whether this is critical enough to justify a new release candidate, because that decision has to factor in the costs. From my perspective, not fixing the bug in Histogram means that the wrong behaviour will remain in place for three more months, potentially affecting and angering more users when the behaviour will finally change in 1.76 (assuming that not many (new) users are going to check boost.org/patches). It the cost of delaying the release by a few days, I think it is worth it. If the cost involved is very large, then publishing the patch on http://boost.org/patches is a feasible solution, sure.
> Not many users check /patches without encouragement, but users read
> the release notes and at the very top of the 1.75 release notes would
> be a warning (emboldened if necessary) to patch Histogram, with a link
> to the file on /patches
Ok. Many consumers use Boost Histogram through its Python wrapper and we can fix the bug there anyway (the Python wrapper is a separate project not tied to the Boost release cycle).
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk