No surprises, as char16_t is transparently handled by QChar overloads. Ok, one surprise: we seem to have QChar <> QByteArray relational operators, but they don't work for char16_t. Probably members of QChar, so LHS implicit conversions are disabled. Didn't investigate, because it needs to be fixed at some point anyway, but that point is not now. Change-Id: I74e1c9bdd168e6480e18d7d86c1f13412e718a32 Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io> |
||
|---|---|---|
| .. | ||
| qbytearray | ||
| qbytearraylist | ||
| qbytearraymatcher | ||
| qbytedatabuffer | ||
| qchar | ||
| qcollator | ||
| qlatin1string | ||
| qlocale | ||
| qregexp | ||
| qregularexpression | ||
| qstring | ||
| qstring_no_cast_from_bytearray | ||
| qstringapisymmetry | ||
| qstringbuilder | ||
| qstringiterator | ||
| qstringlist | ||
| qstringmatcher | ||
| qstringref | ||
| qstringview | ||
| qtextboundaryfinder | ||
| text.pro | ||