Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-111875

Consider adding non-[[nodiscard]] specializations of QtConcurrent::run which returns QFuture<void>

    XMLWordPrintable

Details

    • Task
    • Resolution: Unresolved
    • P3: Somewhat important
    • None
    • None
    • Core: QtConcurrent
    • None
    • 5

    Description

      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
      

      Attachments

        Activity

          People

            cnn Qt Core & Network
            manordheim MÃ¥rten Nordheim
            Vladimir Minenko Vladimir Minenko
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: