-
Task
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
None
-
None
-
5
Running a function returning void could often be a fire-and-forget scenario, or it may even emit signals later. So having QtConcurrent::run() marked nodiscard for all return-types means users must use Q_UNUSED (or its expanded from) to ignore the warning it produces.
void doThing(); ... QtConcurrent::run(doThing); // currently: warning of unused return value ... QFuture<void> future = QtConcurrent::run(doThing); // OK, but... Q_UNUSED(future); // ... it's unused
| For Gerrit Dashboard: QTBUG-111875 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 492990,4 | QtConcurrent::run: point return value ignorers to QThreadPool::start(Callable&&) | dev | qt/qtbase | Status: MERGED | +2 | 0 |
| 493019,2 | [docs] Link from QtConcurent::run() to QThreadPool::start(Callable&&) | dev | qt/qtbase | Status: MERGED | +2 | 0 |
| 494687,2 | [docs] Link from QtConcurent::run() to QThreadPool::start(Callable&&) | 6.5 | qt/qtbase | Status: MERGED | +2 | 0 |
| 494688,2 | [docs] Link from QtConcurent::run() to QThreadPool::start(Callable&&) | 6.6 | qt/qtbase | Status: MERGED | +2 | 0 |
| 494692,3 | [docs] Link from QtConcurent::run() to QThreadPool::start(Callable&&) | tqtc/lts-5.15 | qt/tqtc-qtbase | Status: MERGED | +2 | 0 |
| 494693,2 | [docs] Link from QtConcurent::run() to QThreadPool::start(Callable&&) | tqtc/lts-6.2 | qt/tqtc-qtbase | Status: MERGED | +2 | 0 |