Well, every time I use (or try to use) QStringView I encounter the problem of missing methods/functionality. The same applies to the Qt containers. So “someone else’s problem” affects customers - what’s the point of having fast hash if it misses features customer needs? Writing containers is fun, but who’s going to support them? I am not really against Qt containers, but I have some doubts that QtCompany has enough manpower or desire to support those.
Иван Комиссаров > 23 дек. 2019 г., в 11:11, Alberto Mardegan <[email protected]> > написал(а): > > On 20/12/19 13:47, Giuseppe D'Angelo via Development wrote: >> Just to be devil's advocate, there is... As much as it's fun and >> everything implementing a container, just using std::unordered_map would >> have minimal effort on our side ("someone else's problem", and it's not >> even a random 3rd party, but a mandatory prerequisite for building Qt), > > I'm not sure the "someone else's problem" argument would go down very > well with Qt customers. :-) > > Using std::* classes in the Qt implementation is not a bad idea, but > only as long as their performance is top-notch. Otherwise if Qt just > becomes "a convenient wrapper of the STL", people who care most about > performance will simply go for the latter. > > Ciao, > Alberto > > -- > http://www.mardy.it - Geek in un lingua international > _______________________________________________ > Development mailing list > [email protected] > https://lists.qt-project.org/listinfo/development _______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
