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 "c
usta added a subscriber: ahmadsamir.
usta added a comment.
@ahmadsamir
TASK DETAIL
https://phabricator.kde.org/T14471
To: usta
Cc: ahmadsamir, nicolasfella, kde-frameworks-devel, usta, LeGast00n, cblack,
michaelh, ngraham, bruns
nicolasfella added a comment.
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
p
usta created this task.
usta triaged this task as "Normal" priority.
usta added a project: Frameworks.
TASK DESCRIPTION
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.
