> and also sometimes
> using the private-ish QFutureInterface to be able to use QFuture to
> its full extent, which makes us feel a little dirty :)
Good not to feel alone :)
Philippe
On Thu, 1 Nov 2018 10:42:36 +0100
Elvis Stansvik wrote:
> There were some discussions last year on
> https://bu
There were some discussions last year on
https://bugreports.qt.io/browse/QTBUG-61928 about the async API future
(pun intended). I'm sure there are a few old mailing list threads too.
I too would be interested in where Qt is heading in this area going
forward. We're using the current QtConcurrent A
Hi,
As part of our work projects we have a framework (named Proof and partly open
sourced). Most part of it is not really interesting outside of our industry,
but one of its basic ideas is heavy usage of future/promise technology with API
similar to one used in Scala. We also have tasks schedul
