Hi Thiago,
On Saturday, 9 September 2017 14:37:00 BST Thiago Macieira wrote:
> On Saturday, 9 September 2017 05:46:49 -03 Sean Harmer wrote:
> > Does anybody have any plans to add such a facility? Or is there some
> > other facility to avoid operator new here for both the QSP and the
> > object it
On Saturday, 9 September 2017 05:46:49 -03 Sean Harmer wrote:
> Does anybody have any plans to add such a facility? Or is there some
> other facility to avoid operator new here for both the QSP and the
> object itself?
There are no plans. We don't have allocators anywhere in Qt, so I doubt this
w
On Saturday, 9 September 2017 11:54:14 BST Giuseppe D'Angelo wrote:
> Il 09/09/2017 10:46, Sean Harmer ha scritto:
> > Does anybody have any plans to add such a facility? Or is there some
> > other facility to avoid operator new here for both the QSP and the
> > object itself?
>
> Just go ahead an
Il 09/09/2017 10:46, Sean Harmer ha scritto:
Does anybody have any plans to add such a facility? Or is there some
other facility to avoid operator new here for both the QSP and the
object itself?
Just go ahead and use std::allocate_shared, or is it in public APIs? Any
such improvement to QShar
Hi,
I have a use case where we need to create, use and destroy a relatively
large number of QSharedPointers rapidly. To avoid the malloc overhead it
would be nice to be able to use a pool of QSharedPointers.
We have QSharedPointer::create() which is analogous to
std::make_shared() that allow
