[Development] Important recent changes in QList/QString/QByteArray

[Andrei Golubev]

If we implement this behaviour.

That's the dilemma that Andrei was talking about. Either solution is valid and
both have a way for you to tell QList to do what you want.
Oh, but it's not a question of "if". It is already done in latest dev this way, the shrinking erase, I mean (not sure who was an author of the original change).

--
Best Regards,
Andrei
________________________________
From: Development <development-bounces at qt-project.org> on behalf of Thiago Macieira <thiago.macieira at intel.com>
Sent: Thursday, September 10, 2020 5:33 AM
To: development at qt-project.org <development at qt-project.org>
Subject: Re: [Development] Important recent changes in QList/QString/QByteArray

On Wednesday, 9 September 2020 06:38:01 PDT Andrei Golubev wrote:
> > I don't understand what this means. Am I supposed to reserve a
> > container to its current size before erasing elements
> > from it, if I don't want the erase to shrink it?
> Yes.

If we implement this behaviour.

That's the dilemma that Andrei was talking about. Either solution is valid and
both have a way for you to tell QList to do what you want.

--
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel DPG Cloud Engineering



_______________________________________________
Development mailing list
Development at qt-project.org
https://lists.qt-project.org/listinfo/development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20200910/4b31203e/attachment-0001.html>