Re: [Development] How qAsConst and qExchange lead to qNN

HI Thiago, On 15.11.22 17:33, Thiago Macieira wrote: > On Tuesday, 15 November 2022 01:42:55 PST Marc Mutz via Development wrote: >>> Returning as an iteratable interface requires that we return a proxy >>> object, like QRegularExpressionMatch, so that the solution is >>> thread-safe. This is

Re: [Development] Problems porting Qt5.15 to Qt 6.2 for OS/2

Thanks Alexey and Fabian - this worked a treat! On 15/11/22 20:08, Fabian Kosmale via Development wrote: Hi, to expand on what Alexey said: Without linking against Qt::Gui, you will not have qpa in your include paths, which in turn means that QPlatformIntegrationFactoryInterface_iid  won't

Re: [Development] How qAsConst and qExchange lead to qNN

Hi Thiago, On 15.11.22 17:25, Thiago Macieira wrote: > On Tuesday, 15 November 2022 00:52:24 PST Marc Mutz via Development wrote: >> That remains to be proven. A rule of thumb for atomics is that they're >> two orders of magnitude slower than a normal int. They also still act as >> optimizer

[Development] Meeting minutes from Qt Release Team meeting 15.11.2022

Qt 6.4 status: - Qt 6.4.1 released - Plan is to release Qt 6.4.2 at the beginning of next year Qt 6.5 status: - Dependency update rounds passed quite well recently in 'dev' - Platform and module freeze will be in effect Fri 25th November - Qt 6.5 feature freeze will be in effect Fri 9th December

Re: [Development] How qAsConst and qExchange lead to qNN

On Tuesday, 15 November 2022 01:42:55 PST Marc Mutz via Development wrote: > > Returning as an iteratable interface requires that we return a proxy > > object, like QRegularExpressionMatch, so that the solution is > > thread-safe. This is neither simple to understand, to code, or to port > >

Re: [Development] How qAsConst and qExchange lead to qNN

On Tuesday, 15 November 2022 00:52:24 PST Marc Mutz via Development wrote: > That remains to be proven. A rule of thumb for atomics is that they're > two orders of magnitude slower than a normal int. They also still act as > optimizer firewalls. With that rule of thumb, copying 50 char16_t's is >

Re: [Development] How qAsConst and qExchange lead to qNN

On Monday, 14 November 2022 23:52:23 PST Marc Mutz via Development wrote: > Unless and until we replace all QString/QStringView overload sets with a > single QAnyStringView function (possibly accompanied by a QString > Q_WEAK_OVERLOAD), we can't make QString implicitly convertible from > char16_t

[Development] HEADS-UP: Qt 6.5 Platform and Module Freeze is almost there...

Hi all, Kindly reminder: - Qt 6.5 platform and module freeze will be in effect Fri 25th November 2022. So only a bit more than a week left. * All new modules needs to be in CI and qt5.git (if needed) at that point. Otherwise those will be postponed to Qt 6.6 (or with granted exception those

Re: [Development] How qAsConst and qExchange lead to qNN

On Tue, 15 Nov 2022 08:52:24 + Marc Mutz via Development wrote: > There's nothing inherently Qt-ish about owning containers. Yes and no, because owning containers are part of the very "Qt-ish" Implicit Sharing idiom, which one is _great_ for the ease of use, safety and optimization it

[Development] [Announce] Qt 6.4.1 Released

Hi all! We have released Qt 6.4.1 today, see https://www.qt.io/blog/qt-6.4.1-released Big thanks to everyone involved! Br, Jani Heikkinen Release Manager ___ Announce mailing list annou...@qt-project.org https://lists.qt-project.org/listinfo/announce

Re: [Development] How qAsConst and qExchange lead to qNN

On 14.11.22 22:17, Thiago Macieira wrote: > On Monday, 14 November 2022 12:53:19 PST Marc Mutz via Development wrote: >>> I don't think we will ever change return types. >> >> Your short interjections would be more valuable if you didn't just state >> an opinion, but also give rationale ;-) > >

Re: [Development] Problems porting Qt5.15 to Qt 6.2 for OS/2

Hi, to expand on what Alexey said: Without linking against Qt::Gui, you will not have qpa in your include paths, which in turn means that QPlatformIntegrationFactoryInterface_iid won't be macro-expanded to the string literals that is defined in qplatformintegrationplugin.h. In turn, moc

Re: [Development] Problems porting Qt5.15 to Qt 6.2 for OS/2

Hi, Please try to add LIBRARIES Qt::Gui to the qt_internal_add_plugin call in https://github.com/psmedley/qt6-os2/blob/main/src/plugins/platforms/os2/CMakeLists.txt Regards, Alexey. From: Development on behalf of Paul Smedley Sent: Tuesday, November 15,

[Development] Problems porting Qt5.15 to Qt 6.2 for OS/2

Hi All, I'm attempting to update the OS/2 port of Qt 5.15 (https://github.com/bitwiseworks/qtbase-os2) to Qt 6.2.4 (https://github.com/psmedley/qt6-os2) Things are going pretty well and I have a number of DLLs built, howeever I'm now stuck on building the OS/2 plugin. I'm getting the

Re: [Development] How qAsConst and qExchange lead to qNN

On 15.11.22 08:14, Ulf Hermann via Development wrote: >>> So, if the method immediately converts whatever it gets to QList or >>> QString, then there is no point in passing it a span or view. >> >> My point is that there _is_. Citing my blog post: >> >>     callConsumeQStringHelloWorld(): > >

Re: [Development] How qAsConst and qExchange lead to qNN

On 14.11.22 23:04, A. Pönitz wrote: >> Marc’s proposal of a Non-Owning Interface is already >> become manifest in QRegion::begin/end >> >> https://doc.qt.io/qt-6/qregion.html#begin >> >> allowing us to write >> >> >> for (auto rect : region) doSomethingWith(rect); > Yes, and that's fine [but not