Date: Thu, 12 Nov 2020 15:38:36 +0100
On Thu, Nov 12, 2020 at 05:14:52PM +0300, Antony Polukhin via Std-Proposals wrote:
> ср, 11 нояб. 2020 г. в 20:32, Kilian Henneberger via Std-Proposals
> <std-proposals_at_[hidden]>:
> >
> > Hello everyone,
> > if I am informed correctly, P0881 (https://wg21.link/P0881) has been
> > approved for C++23.
> > And I assume this is no new idea (also not to C++), but what do you
> > think about adding a stacktrace to std::exception?
> This is a very good idea that was not discussed, because this seemed
> to be an ABI breaking change.
Wouldn't that add significant run-time overhead to every throw
expression?
This really needs to be opt-in, but in that case you can just get the
stacktrace in your exception's constructor?
Christof
> ср, 11 нояб. 2020 г. в 20:32, Kilian Henneberger via Std-Proposals
> <std-proposals_at_[hidden]>:
> >
> > Hello everyone,
> > if I am informed correctly, P0881 (https://wg21.link/P0881) has been
> > approved for C++23.
> > And I assume this is no new idea (also not to C++), but what do you
> > think about adding a stacktrace to std::exception?
> This is a very good idea that was not discussed, because this seemed
> to be an ABI breaking change.
Wouldn't that add significant run-time overhead to every throw
expression?
This really needs to be opt-in, but in that case you can just get the
stacktrace in your exception's constructor?
Christof
-- http://cmeerw.org sip:cmeerw at cmeerw.org mailto:cmeerw at cmeerw.org xmpp:cmeerw at cmeerw.org
Received on 2020-11-12 08:38:43