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

Tony Van Eerd tvaneerd at rim.com
Mon Nov 19 19:36:31 CET 2012


Yes, that is what I meant to imply.  Don't wait, but look at what is currently on the table, either for ideas, or to add ideas to.

Implementing something that works is a great way to influence the standard.



> -----Original Message-----
> From: development-bounces+tvaneerd=rim.com at qt-project.org
> [mailto:development-bounces+tvaneerd=rim.com at qt-project.org] On Behalf
> Of Thiago Macieira
> Sent: Friday, November 16, 2012 6:58 PM
> To: development at qt-project.org
> Subject: Re: [Development] The future of QFuture, and QtConcurrent (was
> "Is QtConcurrent's code generator still in use?")
> 
> On sexta-feira, 16 de novembro de 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.
> 
> We can't wait for C++1y, but we should instead try and influence it by
> designing something nice.
> 
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel Open Source Technology Center

---------------------------------------------------------------------
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.



More information about the Development mailing list