On Mon, Apr 27, 2020 at 7:37 AM Niall Douglas
On 27/04/2020 15:01, Marshall Clow wrote:
On Mon, Apr 27, 2020 at 4:03 AM Niall Douglas via Boost
mailto:boost@lists.boost.org> wrote: I assume it is too late for a segfault fix in Outcome for 1.73?
Tell me more, please.
* How likely is someone to run into this?
1. If in a Debug build.
2. If using Experimental.Outcome with a status_code_ptr.
[Letting people know what's up] After discussing this with Niall and the other release managers, we've determined: * This code was in 1.70/71/72. * It only happens with assertions enabled. and decided: * If we do an RC2, then we will include this. * This is not sufficient to justify an RC2 by itself. Unless something comes up, I'm planning on making the 1.73.0 release tonight/tomorrow morning -- Marshall