BUILD UNSTABLE
Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/800/
Project:
kf5-qt5 FreeBSDQt5.15
Date of build:
Thu, 20 May 2021 01:13:36 +
Build duration:
9 min 54 sec and counting
JUnit Tests
Name: projectro
BUILD SUCCESS
Build URL
https://build.kde.org/job/Frameworks/job/kservice/job/kf5-qt5%20FreeBSDQt5.15/132/
Project:
kf5-qt5 FreeBSDQt5.15
Date of build:
Wed, 19 May 2021 14:02:16 +
Build duration:
1 min 26 sec and counting
JUnit Tests
Name: proje
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
