According to Repology[1] all distros who supply qt5.15.x already using 5.15.2
and because of API changes on 5.15.2, i believe it will be much
better to switch 5.15.0 -> 5.15.2 to make things easier such as usage of QString append(QStringView str) [2][3]
[1] https://repology.org/project/qt/badges
[2] https://invent.kde.org/pim/kpimtextedit/-/merge_requests/11#note_233246
[3] https://doc.qt.io/qt-5/qstring.html#append-5
Do we actually *want* to use the API that has been introduced in production?
From QStringView:: toInt:
Note: This method has been added in 5.15.2 to simplify writing code that is portable between Qt 5.15 and Qt 6. The implementation is not tuned for performance in Qt 5.
Anything other than the methods that were added for "portability at the expense of performance", should be OK, famous last words™. :)
I've been bitten twice by the QStringView API in Qt5, it has too many surprises, basically because upstream decided to make "code" portable any which way... but I digress.
Since QStringRef is in a Qt6 compat module, I think QStringView should wait until we branch KF6; we also get QStrinTokenizer Qt6 (yes, it means we might scramble a bit between when we branch KF6 and the first release to fix affected public API's, but I think that's safer).