On 15/11/2020 01:37, Thiago Macieira wrote:
Anyway, the question remains: can we remove the configure-time check and assume std::future and std::async (C++11 standard library features) are present?
The alternative is reimplement QThread::create in a way that doesn't need async/future at all. It's just kind of annoying that that's the only (?) building block provided by the stdlib to apply decay-copy, call it in the new thread in a type-erased way, destroy the data when done, etc.
I'm not exactly volunteering. Also, it can be done after 6.0 without breaking ABI (it just depends on one exported symbol, the rest is inline).
Thanks, -- Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com KDAB - The Qt, C++ and OpenGL Experts
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
