On Wednesday, 2 November 2022 09:40:08 PDT Marc Mutz via Development wrote:
> So, since the time to FF for 6.5 is too short, we're considering to add
> a QSpan as private API for 6.5 with the intent to make it public API in
> 6.6 and by the next LTS to have rolled it out over the code base.
>
> Op
Hi,
If you've ever used std::span (or gsl::span, or llvm::ArrayRef, or ...),
you'll agree that it's nothing short of addictive. And for Qt, in
particular, it's a step toward escaping the lock-in caused by owning NIH
vocabulary types.
As such, std::span is most useful when used at the ABI bound
On Wednesday, 2 November 2022 07:25:25 PDT Marc Mutz via Development wrote:
>QT_GUARD_INCLUDE_OF___
>
> Example:
>
>QT_GUARD_INCLUDE_OF_QTCORE_IO_QIODEVICE_H
We don't need to make it THAT verbose. But inserting the module name makes
sense, because the "official" include is .
I'd also s
Hi,
This is just an anchor email to group the individual upcoming threads
together. Please only reply to it to open a new topic.
On the last QtCS, we've talked a bit about when the right time would be
for Qt 6 to switch to require C++20
(https://wiki.qt.io/Qt_Contributors_Summit_2022_-_Program
> On 2 Nov 2022, at 15:25, Marc Mutz via Development
> wrote:
>
> Hi Volker,
>
> On 14.10.22 17:12, Volker Hilsheimer via Development wrote:
>> Anyway, I’ve added the respective text to the coding convention wiki
>> page.
>> https://wiki.qt.io/Coding_Conventions
>
> Having read the thread in
Hi Volker,
On 14.10.22 17:12, Volker Hilsheimer via Development wrote:
> Anyway, I’ve added the respective text to the coding convention wiki
> page.
> https://wiki.qt.io/Coding_Conventions
Having read the thread in total, I'm surprised about this outcome.
AFAIK, we haven't had problems with tr
