[Development] Use of Standard Library containers in Qt source code

[Cristian Adam]

On Thu, Jul 7, 2016 at 12:06 PM, Marco Bubke <Marco.Bubke at qt.io> wrote:

> I think it simply a question of time to get used to the STL. You get used
> to many things.
>
> I think we should mind about the new features of C++ which are coming,
> which cannot integrated very well with Qt because we use a different idiom.
>
> I really think we should make it easier for the developer but if we
> provide no way to go the fast path do we really make it easier?
>
> If the context is changing over time, is it not smart to reevaluate
> decision again and maybe go a different route? I don't mean to do it all
> the time but maybe there is a middle path between different
> "fundamentalisms". [image: 😉]
>
Luckily there's Copper Spice, and it seems they want to be the more
*modern* C++ Qt library.

Their latest presentation
<https://github.com/boostcon/cppnow_presentations_2016/blob/master/00_tuesday/copperspice_the_next_generation_of_signals.pdf>
has
at page 6 this:

[image: Inline image 1]

The STL containers part is not yet done. Will they keep the move semantics
for the upcoming
containers?

What would QString refactor would bring? UTF-8? QStringView?

Cheers,
Cristian.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160712/4b416cb0/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OutlookEmoji-😉.png
Type: image/png
Size: 390 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160712/4b416cb0/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: copper_spice_1.3.png
Type: image/png
Size: 92329 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160712/4b416cb0/attachment-0001.png>