feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity
Files
126d1d009e64bc39529cd1a118ad8c22e9f7fdfe
qt-creator/src/libs/utils/futuresynchronizer.cpp

64 lines
1.3 KiB
C++
Raw Normal View History

Use SPDX license identifiers Replace the current license disclaimer in files by a SPDX-License-Identifier. Task-number: QTBUG-67283 Change-Id: I708fd1f9f2b73d60f57cc3568646929117825813 Reviewed-by: Eike Ziller <eike.ziller@qt.io>
2022-08-19 15:59:36 +02:00
// Copyright (C) 2021 The Qt Company Ltd.
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GPL-3.0+ OR GPL-3.0 WITH Qt-GPL-exception-1.0
Introduce Utils::FutureSynchronizer The API is nearly the same as QFutureSynchronizer. The differences are: 1. We don't make this class a template class, however, we are leaving some template methods, like addFuture(). For the scope of future synchronizing there is no need for QFuture<T> API, the QFuture<void> is sufficient. 2. Renamed cancelOnWait() getter to isCancelOnWait() in order to conform more to Qt API naming rules. 3. Removed futures() getter and provided isEmpty() instead. 4. Removed c'tor that takes a future and setFuture(). These 2 methods were superfluous and may easily be substituted with other methods from the existing API. The additional feature is about flushing finished futures. This can be done on demand by a call to flushFinishedFutures(), or is done automatically on every call to addFuture(). Change-Id: I6a323c9481eeeea9235e6b6e3048cef02873da08 Reviewed-by: Eike Ziller <eike.ziller@qt.io>
2021-05-11 16:53:03 +02:00
#include "futuresynchronizer.h"
/*! \class Utils::FutureSynchronizer
\brief The FutureSynchronizer is an enhanced version of QFutureSynchronizer.
*/
namespace Utils {
FutureSynchronizer::~FutureSynchronizer()
{
waitForFinished();
}
bool FutureSynchronizer::isEmpty() const
{
return m_futures.isEmpty();
}
void FutureSynchronizer::waitForFinished()
{
Use Utils::FutureSynchronizer in IosSimulatorToolHandlerPrivate Add a new method: void FutureSynchronizer::cancelAllFutures(). Change-Id: I5a4e1ea3230ac3c0ce9d3f26b751b2c05fe3dfd4 Reviewed-by: Eike Ziller <eike.ziller@qt.io>
2021-05-12 15:58:39 +02:00
if (m_cancelOnWait)
cancelAllFutures();
Introduce Utils::FutureSynchronizer The API is nearly the same as QFutureSynchronizer. The differences are: 1. We don't make this class a template class, however, we are leaving some template methods, like addFuture(). For the scope of future synchronizing there is no need for QFuture<T> API, the QFuture<void> is sufficient. 2. Renamed cancelOnWait() getter to isCancelOnWait() in order to conform more to Qt API naming rules. 3. Removed futures() getter and provided isEmpty() instead. 4. Removed c'tor that takes a future and setFuture(). These 2 methods were superfluous and may easily be substituted with other methods from the existing API. The additional feature is about flushing finished futures. This can be done on demand by a call to flushFinishedFutures(), or is done automatically on every call to addFuture(). Change-Id: I6a323c9481eeeea9235e6b6e3048cef02873da08 Reviewed-by: Eike Ziller <eike.ziller@qt.io>
2021-05-11 16:53:03 +02:00
for (QFuture<void> &future : m_futures)
future.waitForFinished();
clearFutures();
}
Use Utils::FutureSynchronizer in IosSimulatorToolHandlerPrivate Add a new method: void FutureSynchronizer::cancelAllFutures(). Change-Id: I5a4e1ea3230ac3c0ce9d3f26b751b2c05fe3dfd4 Reviewed-by: Eike Ziller <eike.ziller@qt.io>
2021-05-12 15:58:39 +02:00
void FutureSynchronizer::cancelAllFutures()
{
for (QFuture<void> &future : m_futures)
future.cancel();
}
Introduce Utils::FutureSynchronizer The API is nearly the same as QFutureSynchronizer. The differences are: 1. We don't make this class a template class, however, we are leaving some template methods, like addFuture(). For the scope of future synchronizing there is no need for QFuture<T> API, the QFuture<void> is sufficient. 2. Renamed cancelOnWait() getter to isCancelOnWait() in order to conform more to Qt API naming rules. 3. Removed futures() getter and provided isEmpty() instead. 4. Removed c'tor that takes a future and setFuture(). These 2 methods were superfluous and may easily be substituted with other methods from the existing API. The additional feature is about flushing finished futures. This can be done on demand by a call to flushFinishedFutures(), or is done automatically on every call to addFuture(). Change-Id: I6a323c9481eeeea9235e6b6e3048cef02873da08 Reviewed-by: Eike Ziller <eike.ziller@qt.io>
2021-05-11 16:53:03 +02:00
void FutureSynchronizer::clearFutures()
{
m_futures.clear();
}
void FutureSynchronizer::setCancelOnWait(bool enabled)
{
m_cancelOnWait = enabled;
}
bool FutureSynchronizer::isCancelOnWait() const
{
return m_cancelOnWait;
}
void FutureSynchronizer::flushFinishedFutures()
{
QList<QFuture<void>> newFutures;
Port from qAsConst() to std::as_const() We've been requiring C++17 since Qt 6.0, and our qAsConst use finally starts to bother us (QTBUG-99313), so time to port away from it now. Since qAsConst has exactly the same semantics as std::as_const (down to rvalue treatment, constexpr'ness and noexcept'ness), there's really nothing more to it than a global search-and-replace. Task-number: QTBUG-99313 Change-Id: I88edd91395849574436299b8badda21bb93bea39 Reviewed-by: hjk <hjk@qt.io>
2022-10-07 14:46:06 +02:00
for (const QFuture<void> &future : std::as_const(m_futures)) {
Introduce Utils::FutureSynchronizer The API is nearly the same as QFutureSynchronizer. The differences are: 1. We don't make this class a template class, however, we are leaving some template methods, like addFuture(). For the scope of future synchronizing there is no need for QFuture<T> API, the QFuture<void> is sufficient. 2. Renamed cancelOnWait() getter to isCancelOnWait() in order to conform more to Qt API naming rules. 3. Removed futures() getter and provided isEmpty() instead. 4. Removed c'tor that takes a future and setFuture(). These 2 methods were superfluous and may easily be substituted with other methods from the existing API. The additional feature is about flushing finished futures. This can be done on demand by a call to flushFinishedFutures(), or is done automatically on every call to addFuture(). Change-Id: I6a323c9481eeeea9235e6b6e3048cef02873da08 Reviewed-by: Eike Ziller <eike.ziller@qt.io>
2021-05-11 16:53:03 +02:00
if (!future.isFinished())
newFutures.append(future);
}
m_futures = newFutures;
}
} // namespace Utils
Copy Permalink