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

A. Pönitz wrote: > [And since we are at it: It would ease my life (but possibly hamper the > life of my cardiologist) if you wouldn't call it "Qt NIH API". This is > an open insult to people who actively designed these APIs _with > different goals_ than the STL. I personally think it's completely f

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

On Wednesday, 9 November 2022 11:25:32 PST Thiago Macieira wrote: > On Wednesday, 9 November 2022 02:52:15 PST Marc Mutz via Development wrote: > > We can also return spans: > > QSpan actions() const; > > we CANNOT and MUST NOT. Unless you can find a way to return the collection of QActions

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

On Wednesday, 9 November 2022 02:52:15 PST Marc Mutz via Development wrote: > This is the same effect we have with Q*StringView, incl. avoidance of > caller-side construction and destruction of owning containers. Indeed, which is WRONG. Our API should default to passing QStrings for simplicity an

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

On Wednesday, 9 November 2022 02:52:15 PST Marc Mutz via Development wrote: > We can also return spans: > > QSpan actions() const; we CANNOT and MUST NOT. -- Thiago Macieira - thiago.macieira (AT) intel.com Cloud Software Architect - Intel DCAI Cloud Engineering ___

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

Hi, let me mention that I've been pondering all that hairy stuff just recently when trying to come up with a solution for how to map QList*> and QQmlListProperty to each other without exposing people to dangling references and without copying and allocating all the time. One thing we could do

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

> On 9 Nov 2022, at 12:49, Marc Mutz via Development > wrote: > > Hi Volker, > > On 09.11.22 10:15, Volker Hilsheimer wrote: >> But I do believe that we can add APIs that are iterator and ranges friendly >> to Qt without tossing out the baby with the bathwater and without breaking >> tons o

[Development] [Announce] Qt Installer Framework and Online Installer 4.5.0 released

Hi all, we have released Qt Installer Framework and Online Installer 4.5.0 today! Thank you to the development team & everyone involved 😊. Please see the blog post: https://www.qt.io/blog/qt-installer-framework-and-online-installer-4.5.0-released Best regards, Tarja Sundqvist Release manager _

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

Hi Volker, On 09.11.22 10:15, Volker Hilsheimer wrote: > But I do believe that we can add APIs that are iterator and ranges friendly > to Qt without tossing out the baby with the bathwater and without breaking > tons of code and patterns. For APIs where we simply return a stored QList we > want

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

Hi Ulf, On 09.11.22 08:18, Ulf Hermann via Development wrote: >> I don't want to take the Qt containers away from Qt users. I want to get >> rid of their use in our APIs, so that both the Qt implementation as well >> as our users are free to choose the best container for their needs >> instead of

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

> Volker Hilsheimer via Development wrote: nice pragmatic overview :) Philippe On Wed, 9 Nov 2022 09:15:16 + Volker Hilsheimer via Development wrote: > Hi, > > > On 8 Nov 2022, at 22:20, Marc Mutz via Development > > wrote: > > To summarize: > > - I will not accept responsibility for a

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

Hi, > On 8 Nov 2022, at 22:20, Marc Mutz via Development > wrote: > To summarize: > - I will not accept responsibility for any container rewrites in any of > the Qt major version changes. I was not involved in any of these > decisions, and where I was involved in the discussion, my suggestio