Details
-
Suggestion
-
Resolution: Fixed
-
P2: Important
-
6.6.0 Beta2
-
None
-
3
-
ab910e09c (dev)
-
Foundation Sprint 90, Foundation Sprint 91, Foundation Sprint 92, Foundation Sprint 93, Foundations Sprint 94, Foundations Sprint 95, Foundations Sprint 96, Foundations Sprint 97
Description
When Qt 6.6 added support for q(u)int128, it forgot to add QTest::toString() support for it. Without it, it's pretty hard to write tests using those types.
We already have a local implementation in tst_qglobal.cpp, just need to extract it, polish it, and somehow get it into tst_selftest.
TODO: Can we use qint128 under QT_SUPPORTS_INT128 protection, or do we require builds with and without __int128 support to be BC?
Acceptance criteria:
- QTest::toString() works with qint128 and quint128 on all QT_SUPPORTS_INT128 platforms
- not by falling back on one of the narrower integer types
- checked by tst_selftest
Attachments
For Gerrit Dashboard: QTBUG-117011 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
504075,11 | Long live QDebug::operator<<(q(u)int128)! | dev | qt/qtbase | Status: MERGED | +2 | 0 |