Ievgenii Meshcheriakov 2c0bdd38cb tst_qstringapisymmetry: Don't pretend that QByteArray contains UTF-8 ... The name of is_utf8_encoded type seems to imply that QByteArray and const char * contain UTF-8 encoded data. This is not always the case. When used with QByteArray API, those types are handled as containing ASCII-only. It's only when used with APIs of other classes (QString, QLatin1String) they are handled as UTF-8. This renames the check to is_bytearray_like_v and clarifies its usage. No need to handle QUtf8StringView this way because it works just fine with the current testcases. While at it, also remove unused is_latin1_encoded trait. Task-number: QTBUG-92021 Change-Id: I44e40cf3c0dd07e5b3cf1e47ff7a04f1c548aa97 Reviewed-by: Edward Welbourne <edward.welbourne@qt.io> Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>		2021-09-09 15:02:02 +02:00
..
.gitignore	Move text-related code out of corelib/tools/ to corelib/text/	2019-07-10 17:05:30 +02:00
CMakeLists.txt	CMake: Regenerate projects to use new qt_internal_ API	2020-09-23 16:59:06 +02:00
tst_qstringapisymmetry.cpp	tst_qstringapisymmetry: Don't pretend that QByteArray contains UTF-8	2021-09-09 15:02:02 +02:00