On Tuesday, 18 June 2019 22:34:02 PDT Mutz, Marc via Development wrote: > I'm not concerned about bugs. I'm concerned that making Qt's pimpl_ptr > public API constrains how Qt itself is implemented. Sure, we can add yet > another pimpl_ptr and make that public again, by the same rationale. But > what purpose do four different Qt pimpl_ptrs serve, which all need to be > supported? That makes no sense. We had the same issues with QSharedData, > btw. And since that was public, we had to introduce QtPrivate::RefCount.
They serve different purposes. QSharedData could use QtPrivate::RefCount for its refcount if we wanted to. The reason it doesn't is that QSharedData predates RefCount by close to a decade. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel System Software Products _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
