Giuseppe D'Angelo 594abde1a2 Enforce that statically allocated array-like containers have 0 capacity ... It has been the case for both QStringLiteral and QByteArrayLiteral since Qt 5.0, and Q_ARRAY_LITERAL since Qt 6.0. Since it's definitely surprising, add a note in the docs, which is "somehow" consistent with the interpretation of capacity as the biggest possible size before we reallocate. Since it's 0, any manipulation of the size will cause a reallocation. (Alternatively: the capacity() is for how many elements memory was requested from the free store. No memory was allocated, so 0...) Task-number: QTBUG-84069 Change-Id: I5c7d21a22d1bd8b8d9b71143e33d537ca0224acd Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>		2020-05-14 14:19:47 +02:00
..
.gitignore	…
CMakeLists.txt	Port qtbase/tests/auto/corelib/text tests to CMake	2020-04-27 14:34:51 +02:00
double_data.h	…
qstring.pro	Don't try to define QT_NO_CAST_TO_ASCII when the test undefines it	2019-10-25 11:41:44 +02:00
tst_qstring.cpp	Enforce that statically allocated array-like containers have 0 capacity	2020-05-14 14:19:47 +02:00
tst_qstring_mac.mm	…