Boost logo

Boost :

Subject: Re: [boost] Boost 1.61.0 Release Candidate 1
From: Vladimir Prus (vladimir.prus_at_[hidden])
Date: 2016-05-06 02:31:23

On 06/05/2016 00:44, Frank Mori Hess wrote:
> On Thu, May 5, 2016 at 5:10 PM, Vladimir Prus <vladimir.prus_at_[hidden]> wrote:
>>> There are two tickets:
>> Thanks - that sounds like unfortunate situation, and that boost::any can't
>> do much, as its constructor is designed to accept anything.
>> I've cherry-picked that commit - could you double-check that the master
>> branch of the superproject is now fine?
> The commits weren't in master because I made the fix after master was
> already closed for 1.61. I was waiting for it to re-open after the
> release. The fixes were just a work-around for a broken compiler, I
> really don't see why the release process should be bothering with
> them.

I would guess Stephan is in better position to say whether it's indeed
broken compiler - from his blog post it sounds like accurate implementation
of a broken/suboptimal specification.

Anyway, boost::signals2, boost::any and boost::variant seem like fairly important
parts of Boost, there are already two independent bug reports, and having this
problem on the most recent version of a popular compiler is somewhat embarrassing.
If it can be solved by delaying the release by a day or so, it seems reasonable.

Do you see any reason why this commit might explode on master?


Vladimir Prus

Boost list run by bdawes at, gregod at, cpdaniel at, john at