[Development] The future of smart pointers in Qt API

[Giuseppe D'Angelo]

Il 03/02/20 17:56, Jason H ha scritto:
> As a result, the code of a Qt-using program should be readable by average developers not big into C++. 

But no one is imposing super-advanced C++ features on Qt users and Qt 
applications...


> Meanwhile, it also does not serve anyone to duplicate stl. I do not know where the threshold is for duplication (probably pretty high) but I would encourage the threshold to be low for augmentation.

I've asked "what's wrong with the C++ smart pointers" a dozen times and 
never received a satisfactory answer.

As a counter-example: I didn't complain at all about having a QFuture 
with a different feature set than std::future (cf. the other thread on 
this topic). Why is that? Because std::future lacks critical features 
(e.g. continuations); QFuture aims at filling that gap, and I'm 
super-fine with that. Do you see me complaining about QString vs u16string?

My 2 c,
-- 
Giuseppe D'Angelo | giuseppe.dangelo at 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4329 bytes
Desc: Firma crittografica S/MIME
URL: <http://lists.qt-project.org/pipermail/development/attachments/20200203/e0252276/attachment.bin>