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

[Tony Van Eerd]

Nope.  
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3378.pdf


> -----Original Message-----
> From: Olivier Goffart [mailto:olivier at woboq.com]
> Sent: Friday, November 16, 2012 6:58 PM
> To: Tony Van Eerd
> Cc: development at qt-project.org
> Subject: Re: [Development] The future of QFuture, and QtConcurrent (was
> "Is QtConcurrent's code generator still in use?")
> 
> On Friday 16 November 2012 23:46:32 Tony Van Eerd wrote:
> > C++1y (ie whatever the next standard might be called) will likely
> have even
> > more threading options. Including an "executor" model where you queue
> up
> > std::functions to be run on background thread(s).  But the background
> > threading is "configurable" by the fact that the executor object
> isn't
> > completely hidden from you (like it is with std::async(), etc).
> >
> > Maybe we should model something along those lines.  I've used that
> model
> > quite successfully in the past.
> >
> > I can probably find the current proposal(s) in the standards
> committee if
> > anyone is interested.
> 
> Are you refering to this one?
> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3429.pdf
> 
> 
> --
> Olivier
> 
> Woboq - Qt services and support - http://woboq.com


---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.