ahmadsamir added a comment.
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). TASK DETAIL https://phabricator.kde.org/T14471 To: ahmadsamir Cc: ahmadsamir, nicolasfella, kde-frameworks-devel, usta, LeGast00n, cblack, michaelh, ngraham, bruns
