Jarek Kobus 79fd1cb2c6 Reuse the non blocking implementation for blocking one ... Replace the implementation of blockingMappedReduced(): after calling non-blocking version of mappedReduced() we are getting the future object, so we may call in sequence result(), which will block and return the result when the all tasks are done. The same is done with blockigMapped(), which calls blockingMappedReduced() with a custom reduce function. Looks like with this pattern we can reuse the non-blocking version for implementing blocking version of mapped / filtered methods. Task-number: QTBUG-83918 Change-Id: I7f240cfbd04834d551ff79d717b72194a26996d7 Reviewed-by: Sona Kurazyan <sona.kurazyan@qt.io>		2020-06-05 12:09:59 +02:00
..
.gitignore	Move QtConcurrent into its own module	2012-02-05 17:49:16 +01:00
.prev_CMakeLists.txt	Post merge fixes	2019-11-25 14:53:27 +00:00
CMakeLists.txt	Get rid of some QT_STRICT_ITERATORS leftover	2020-03-05 16:08:30 +01:00
functions.h	Add more tests for QtConcurrent::filterReduced()	2020-05-07 15:23:58 +02:00
qtconcurrentmap.pro	Remove QLinkedList	2020-02-19 21:01:07 +01:00
tst_qtconcurrentmap.cpp	Reuse the non blocking implementation for blocking one	2020-06-05 12:09:59 +02:00