Hi, Il 05/11/18 12:08, Jean-Michaël Celerier ha scritto:
It's not only about breaking APIs but also breaking current observable behaviour - i.e. performance. Currently if you're passing data across threads - e.g. compute something in a thread and pass the result to the main thread to display it - you generally pass a QVector / QList / QWhatever that does implicit sharing, because the signal-slot mechanism will do a copy of the object in any case across threads and doing two atomic operations for a QVector copy is cheaper than creating a new std::vector, calling malloc, and copying 500 ints however you look at it. What is the option if Qt opts out from this ? put everything in shared_ptr ?
Hold on -- I don't think that anyone wants to make Qt containers NOT implictly shared. In other words, Qt 6 containers will be implictly shared just as today. It would be a gigantic break if we suddenly made them not shared.
My 2 c, -- 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: Firma crittografica S/MIME
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
