Date: Thu, 29 Apr 2021 17:32:28 +0100
On Thu, 29 Apr 2021 at 17:28, Andrey Semashev via Std-Proposals <
std-proposals_at_[hidden]> wrote:
> On 4/29/21 7:22 PM, Edward Catmur wrote:
> > On Thu, 29 Apr 2021 at 17:19, Andrey Semashev via Std-Proposals
> > <std-proposals_at_[hidden] <mailto:std-proposals_at_[hidden]>>
>
> > wrote:
> >
> > Whether that call to another TU is logging or something else is
> > irrelevant. The important part is that your suggested way of
> detecting
> > the need for a stacktrace doesn't work in general.
> >
> > Or rather, it doesn't work in one particular use case.
>
> Rather it only works in one trivial use case.
>
It works in the most performance-sensitive case. Perhaps you can get your
vendor to give you a compiler flag or attribute to suppress exception
stacktraces.
std-proposals_at_[hidden]> wrote:
> On 4/29/21 7:22 PM, Edward Catmur wrote:
> > On Thu, 29 Apr 2021 at 17:19, Andrey Semashev via Std-Proposals
> > <std-proposals_at_[hidden] <mailto:std-proposals_at_[hidden]>>
>
> > wrote:
> >
> > Whether that call to another TU is logging or something else is
> > irrelevant. The important part is that your suggested way of
> detecting
> > the need for a stacktrace doesn't work in general.
> >
> > Or rather, it doesn't work in one particular use case.
>
> Rather it only works in one trivial use case.
>
It works in the most performance-sensitive case. Perhaps you can get your
vendor to give you a compiler flag or attribute to suppress exception
stacktraces.
Received on 2021-04-29 11:32:40