-
Bug
-
Resolution: Fixed
-
P2: Important
-
6.1.3, 6.2.6, 6.3.2, 6.4.1, 6.5.0 Beta1
-
None
-
8
-
028c367f7 (dev), 9b4b32ec9 (dev), 7f38f9f39 (dev), f535958c2 (dev)
-
Foundation Sprint 77, Foundation Sprint 78, Foundations Sprint 79
Due to a missing constraint the perfectly-forwarding overload wins for mutable QList<T> and returns a QFuture<QList<T>. Expected: the QList overload is chosen and returns a multi-valued QFuture<T>.
- resulted from
-
QTBUG-86713 Add support for creating a ready QFuture
-
- Closed
-
| For Gerrit Dashboard: QTBUG-109677 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 465593,13 | Deprecate QtFuture::makeReadyFuture() | dev | qt/qtbase | Status: MERGED | +2 | 0 |
| 466732,11 | Long live QtFuture::makeReadyRangeFuture() | dev | qt/qtbase | Status: MERGED | +2 | 0 |
| 467791,7 | Long live QtFuture::makeReadyVoidFuture() and QtFuture::makeReadyValueFuture() | dev | qt/qtbase | Status: MERGED | +2 | 0 |
| 467793,3 | Do not use deprecated QtFuture::makeReadyFuture() | dev | qt/qtwebchannel | Status: MERGED | +2 | 0 |