On Fri, 30 Aug 2024 at 06:17, Ville Voutilainen
wrote:
>
> On Fri, 30 Aug 2024 at 04:59, Thiago Macieira
> wrote:
>
> > Said macro should be tied to the precondition itself, if we can. I haven't
> > looked at the syntax: can one macro in one location expand to preconditions-
> > or-noexcept-or-b
On Fri, 30 Aug 2024 at 04:59, Thiago Macieira wrote:
> Said macro should be tied to the precondition itself, if we can. I haven't
> looked at the syntax: can one macro in one location expand to preconditions-
> or-noexcept-or-both?
Yes. Here's an example of the syntax for you:
void f(int x) noe
On Thursday 29 August 2024 18:14:37 GMT-7 Ville Voutilainen wrote:
> It's very unlikely to be anything other than an incompatible build.
I presume you are answering that for the standard library.
If the standard library will have an incompatible build, then by definition
ours that depends on the
On Thu, 29 Aug 2024 at 18:34, Thiago Macieira wrote:
>
> On Thursday 29 August 2024 06:43:58 GMT-7 Marc Mutz via Development wrote:
> > I'm ok with 1-3, I'm not ok with 4.
> >
> > The state of the art is what the std prescribes, not what a stdlib
> > implementation does. stdlibs are magic; they ca
On Thursday 29 August 2024 13:33:55 GMT-7 Marc Mutz via Development wrote:
> On 29.08.24 17:31, Thiago Macieira wrote:
> > What I'd like to change is:
> > - for inline code, where the function's noexceptness is likely to be used
> > in a>
> > noexcept expression elsewhere and that causes slower
On 29.08.24 17:31, Thiago Macieira wrote:
> What I'd like to change is:
> - for inline code, where the function's noexceptness is likely to be used in
> a
> noexcept expression elsewhere and that causes slower code to be used
How does that square with being tool-checkable? That sounds like a
On Thursday 29 August 2024 06:43:58 GMT-7 Marc Mutz via Development wrote:
> I'm ok with 1-3, I'm not ok with 4.
>
> The state of the art is what the std prescribes, not what a stdlib
> implementation does. stdlibs are magic; they can theoretically remove
> the noexcept for new code and keep it fo
I'm ok with 1-3, I'm not ok with 4.
The state of the art is what the std prescribes, not what a stdlib
implementation does. stdlibs are magic; they can theoretically remove
the noexcept for new code and keep it for old. Or they can let contract
violations pass magically. We can't, at least not w
Maintenance break will be started earlier than planned to allow time for data
migration. Break will start 17:00 UTC / 20:00 Finnish time on Sunday 1.9.2024.
From: Development on behalf of CI
Maintenance Break via Development
Date: Monday, 26. August 2024 at 13.19
To: development@qt-project.or
