The problem is that Qt stuck at some point. We can’t use STL in our API, so we forced to have QVector, …, QSharedPointer, .... On the other hand, we doesn’t develop those classes, because stl already have them. So, we’re missing QUniquePtr, qMakeShared, append(T&&) (yeah, COW, i know) and so on. We have to move from that point somewhere, either extending our classes to make them standard-compatible (when possible) or replace them with stl ones.
Иван Комиссаров 19 нояб. 2016 г., в 12:34, Alexander Nassian <nass...@bitshift-dynamics.de> написал(а): > Will there be now 10 BC discussions every year? At least it feels like. Why > can't it be decided and then accepted by everyone as is? In my personal > opinion I don't care much about BC but I'm happy that it blocks STL usage > because its brutally unnatural and I stumbled so often over different > behaviors of it on different platforms and compilers that I have a real hate > on the STL. > > Beste Grüße / Best regards, > Alexander Nassian _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
