[Development] The future of QFuture, and QtConcurrent (was "Is QtConcurrent's code generator still in use?")

[Sze Howe Koh]

On 14 November 2012 19:17, Sorvig Morten <Morten.Sorvig at digia.com> wrote:
> I think what QtConcurrent really needs is a plan. What do we want it to be? There are several options, and I'd like to offer the "null" option:
>
> QtConcurrent is done. The implementation is not good enough to be used as a base for further development. We should limit ourselves to fixing bugs and making small improvements where we can.
>
> This is in line with moving QtConcurrent out of Qt Core. It also has the advantage of not taking much developer time.

Speaking of which, is there a reason why QFuture* classes are still in
Qt Core? QFuture is meant to be created through QtConcurrent
functions, if I'm not mistaken.


Regards,
Sze-Howe