> And you think Qt provides what MS added to std::vector here, in QVector?
Of course not. I just point the danger of dependencies on the usage of STL APIs, especially corner APIs. I understand the #1 target of Qt is to behave the same on all platforms (as much as possible...). This is what users expects, at least. Philippe On Mon, 21 Nov 2016 09:04:59 +0100 Marc Mutz <marc.m...@kdab.com> wrote: > On Sunday 20 November 2016 23:20:11 Philippe wrote: > > On Sun, 20 Nov 2016 19:49:09 +0100 > > > > Marc Mutz <marc.m...@kdab.com> wrote: > > > I just intended to indicate that with 5.0, when we dropped QT_NO_STL, but > > > failed to take advantage of the STL containers, > > > > ...good that STL containers were not used... Look at _this month_ Visual > > Studio 2017 announcement: > > > > <<<< > > std::vector has been overhauled for correctness and performance: aliasing > > during insertion/emplacement is now correctly handled as required by the > > Standard, the strong exception guarantee is now provided when required by > > the Standard via move_if_noexcept() and other logic, and > > insertion/emplacement perform fewer element operations. > > (https://www.visualstudio.com/en-us/news/releasenotes/vs2017-relnotes) > > > > > > Being the "standard library" does not mean "bug free and equal on all > > platforms". Dependencies with other libraries must be careful checked. > > And you think Qt provides what MS added to std::vector here, in QVector? > > -- > Marc Mutz <marc.m...@kdab.com> | Senior Software Engineer > KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company > Tel: +49-30-521325470 > KDAB - The Qt, C++ and OpenGL Experts > _______________________________________________ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
