Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
6.3.0 Beta2
-
None
-
3
-
e1b8257dee (qt/qtbase/dev) e1b8257dee (qt/tqtc-qtbase/dev) 5dabd52a4a (qt/tqtc-qtbase/6.3.0) 21166bd3c9 (qt/tqtc-qtbase/6.3.0)
-
Team Two Foundation Sprint 52, Team B Foundation Sprint 53
Description
The QFlags test doesn't test the (more interesting) case of QT_TYPESAFE_FLAGS. So we don't know anything about this mode, except the implicit use in QtCore and bootstrap seems to work.
We should actually test both modes (→QTBUG-101304).
Attachments
Issue Links
- blocks
-
QTBUG-101304 Compile tst_qflags both with and w/o QT_TYPESAFE_FLAGS
- Closed
- depends on
-
QTBUG-101299 QCOMPARE() doesn't compile for certain QFlags<T> with QT_TYPESAFE_FLAGS
- Closed
-
QTBUG-101300 QFlags: Missing some bitwise xor operators with QT_TYPESAFE_FLAGS
- Closed
-
QTBUG-101399 QTest::toString() doesn't compile for certain QFlags<T> with QT_TYPESAFE_FLAGS
- Closed
- resulted in
-
QTBUG-101406 Add QT_TYPESAFE_FLAGS to headerclean and fix fallout
- Reported
For Gerrit Dashboard: QTBUG-101294 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
398109,3 | tst_qflags: compile with QT_TYPESAFE_FLAGS | dev | qt/qtbase | Status: MERGED | +2 | 0 |
398112,5 | tst_qflags: test w/and w/o QT_TYPESAFE_FLAGS | dev | qt/qtbase | Status: MERGED | +2 | 0 |
398314,2 | tst_qflags: compile with QT_TYPESAFE_FLAGS | 6.3 | qt/qtbase | Status: MERGED | +2 | 0 |
399582,2 | tst_qflags: test w/and w/o QT_TYPESAFE_FLAGS | 6.3 | qt/qtbase | Status: MERGED | +2 | 0 |