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". [đŸ˜‰] ________________________________ From: Development <development-bounces+marco.bubke=qt...@qt-project.org> on behalf of Martin Smith <martin.sm...@qt.io> Sent: Thursday, July 7, 2016 9:25:18 AM To: AndrĂ© Somers; development@qt-project.org Subject: Re: [Development] Use of Standard Library containers in Qt source code How about a merger of options 3 & 4 for Qt 6.0? A QtSTL that combines the ease of use of the Qt collections with the efficiency of STL algorithms. martin ________________________________ From: Development <development-bounces+martin.smith=qt...@qt-project.org> on behalf of AndrĂ© Somers <an...@familiesomers.nl> Sent: Thursday, July 7, 2016 9:20:10 AM To: development@qt-project.org Subject: Re: [Development] Use of Standard Library containers in Qt source code Op 07/07/2016 om 09:10 schreef Marc Mutz: > On Thursday 07 July 2016 03:00:08 Thiago Macieira wrote: >> In case we're not getting the deserved attention due to Summer vacations, >> I'll post again in a month or so to see if there's any change. > We have The Chief on record saying that we should use whatever is most > efficient > internally (https://codereview.qt-project.org/114327 comment from > 2015-06-15), and you agreeing (ibid, 1st @ 2015-06-16). > > So from my pov, the only question is whether we stay with Option 4 or relax to > Option 5, and I'm fine with either. > I don't think that rules out option 3 either, does it? AndrĂ© _______________________________________________ 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
