[Development] Is QFutureInterface internal like the other d-pointer classes?
Thiago Macieira
thiago.macieira at intel.com
Thu Jul 23 19:14:26 CEST 2015
On Thursday 23 July 2015 16:34:40 Lorenz Haas wrote:
> 2015-07-23 13:20 GMT+02:00 Marc Mutz <marc.mutz at kdab.com>:
> > It's undocumented, and considered private, but since it's a template and
> > thus must be visible, it effectively is public API and falls under the
> > same restrictions for changes as public API. IOW: it cannot change
> > (incompatibly) until Qt 6.
> >
> > If you're fine with that, go ahead and use it in your code.
>
> Thanks for the clarification.
>
> Are there any plans to make QFuture/QFutureInterface (completely)
> public in Qt 6 as a Qt counterpart to std::future/std::promise?
There are no plans on either way. We'll probably have to decide on std::future
when we get to Qt 6.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
More information about the Development
mailing list