using namespace std;
summary
Explains why Qt avoids exposing the C++ standard library in its ABI to keep binaries compatible across libstdc++/libc++ implementations, shows Qt5 using STL internally but keeping Qt types public, and recommends using std::algorithms with Qt containers. Compares QVector versus std::vector (implicit sharing and copy‑on‑write costs), QByteArray/QString versus std::string and std::u16string, advocates string_view for zero‑copy APIs, and notes when to prefer std::unique_ptr, std::thread or Qt alternatives for clarity and performance.
AI-written summary · about
chapters (4)
related talks
55mKEYNOTE: Qt Containers and Algorithms
01h 01mEffective Qt (2017 edition)
59mStrongly Typed Containers
01h 29mWhat Does It Take to Implement the C++ Standard Library?
03mLet's cmakeify the C++ standard library
06mC++ and Qt communities: join the forces
01h 31mNew (& Old) C++ Standard Library Containers - How to Choose the Right Container in C++26 and Beyond
01h 23mAlex Stepanov, Generic Programming in Cpp, and the STL