On Thu, Jul 7, 2016 at 12:06 PM, Marco Bubke <marco.bu...@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.
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
