Re: [Development] Requesting Feature Freeze Exception for C++20 comparison

2023-06-06 Thread Thiago Macieira
On Monday, 5 June 2023 23:45:03 PDT Alex Blasche via Development wrote: > The point of using date and time as example was to proof the concept. This > is an API offer for other maintainers to adopt in their API offering. We > have never made it a condition for features to be adopted by every single

Re: [Development] Requesting Feature Freeze Exception for C++20 comparison

2023-06-05 Thread Alex Blasche via Development
>From: Development on behalf of Volker >Hilsheimer >Lets continue with this for Qt 6.7. >Even if we agree on the naming and can exclude binary compatibility issues, >rolling this out to all (or at least a substantial amount of) existing value >types a

Re: [Development] Requesting Feature Freeze Exception for C++20 comparison

2023-06-05 Thread Volker Hilsheimer via Development
> On 4 Jun 2023, at 23:26, Thiago Macieira wrote: > > On Sunday, 4 June 2023 11:51:54 PDT Marc Mutz via Development wrote: >>> The other problem is I want to take a second, thorough look at your >>> #ifdefs >>> for C++20. I have a feeling some of the changing return types are a recipe >>> for bin

Re: [Development] Requesting Feature Freeze Exception for C++20 comparison

2023-06-04 Thread Thiago Macieira
On Sunday, 4 June 2023 11:51:54 PDT Marc Mutz via Development wrote: > > The other problem is I want to take a second, thorough look at your > > #ifdefs > > for C++20. I have a feeling some of the changing return types are a recipe > > for binary compatibility problems, if not in our own code, then

Re: [Development] Requesting Feature Freeze Exception for C++20 comparison

2023-06-04 Thread Marc Mutz via Development
On 04.06.23 18:16, Thiago Macieira wrote: [...] > The other problem is I want to take a second, thorough look at your #ifdefs > for C++20. I have a feeling some of the changing return types are a recipe for > binary compatibility problems, if not in our own code, then in code that uses > our code.

Re: [Development] Requesting Feature Freeze Exception for C++20 comparison

2023-06-04 Thread Thiago Macieira
On Sunday, 4 June 2023 08:24:14 PDT Ivan Solovev via Development wrote: > Like I wrote, I generally consider this task done, except for the naming > issues. I have an impression that we will be able to come to an agreement > in a reasonable time frame. > > However, if you think that there are more

Re: [Development] Requesting Feature Freeze Exception for C++20 comparison

2023-06-04 Thread Ivan Solovev via Development
PM To: development@qt-project.org Subject: Re: [Development] Requesting Feature Freeze Exception for C++20 comparison On Friday, 2 June 2023 05:18:57 PDT Ivan Solovev via Development wrote: > I'd like to request a Feature Freeze exception for the C++20 comparison > task, due to the

Re: [Development] Requesting Feature Freeze Exception for C++20 comparison

2023-06-02 Thread Thiago Macieira
On Friday, 2 June 2023 05:18:57 PDT Ivan Solovev via Development wrote: > I'd like to request a Feature Freeze exception for the C++20 comparison > task, due to the last-minute discussions about the names of the helper > functions to be used. This is important because these helper functions are > i

[Development] Requesting Feature Freeze Exception for C++20 comparison

2023-06-02 Thread Ivan Solovev via Development
Hi, I'd like to request a Feature Freeze exception for the C++20 comparison task, due to the last-minute discussions about the names of the helper functions to be used. This is important because these helper functions are intended to be exposed as public API. The task is https://bugreports.qt.