On Wednesday 28 August 2024 03:23:52 GMT-7 Volker Hilsheimer via Development
wrote:
> TL;DR: Given that the tradeoff is between two marginally and somewhat
> speculative benefits, it seems to me that a pragmatic (as opposed to
> dogmatic) application of the Lakos rule in the cases where Q_ASSERT i
On Wednesday 28 August 2024 01:07:12 GMT-7 Ville Voutilainen wrote:
> > It starts to get interesting for code that checks on the noexceptness of
> > the content it's calling and use different algorithms. There aren't a lot
> > of those outside of container copy, but they do exist.
>
> Just checkin
Most of this discussion is way beyond my C++ skill level. But I think the
root problem may be that Qt has (at least) two very different user classes.
For users working on mission-critical embedded systems, code rigor is
important. Performance is important. It's worth worrying about the
performa
On Wed, 28 Aug 2024 at 13:26, Volker Hilsheimer via Development
wrote:
> Since Lakos is referenced in this thread, two quotes from the paper [1] that
> resulted in P3155R0 [2], aka “The Lakos Rule”:
>
> On page 5 of [1]:
>
> > What Are We Proposing
> > In order to support effective testing, compi
> On 27 Aug 2024, at 21:21, Thiago Macieira wrote:
>
> On Tuesday 27 August 2024 10:29:05 GMT-7 Ville Voutilainen wrote:
>> On Tue, 27 Aug 2024 at 17:15, Thiago Macieira
> wrote:
>>> The point is that this putative mistake has no consequences, today. It
>>> remains to be seen whether it will wit
On Tue, 27 Aug 2024 at 22:23, Thiago Macieira wrote:
>
> On Tuesday 27 August 2024 10:29:05 GMT-7 Ville Voutilainen wrote:
> > On Tue, 27 Aug 2024 at 17:15, Thiago Macieira
> wrote:
> > > The point is that this putative mistake has no consequences, today. It
> > > remains to be seen whether it wi