[Development] ODP: RFC: Deprecating setSharable / isSharable in our containers and QString
Thiago Macieira
thiago.macieira at intel.com
Fri Feb 21 17:39:59 CET 2014
Em sex 21 fev 2014, às 11:31:32, Nowacki Jedrzej escreveu:
> I agree that the code is fragile and it is not the best api ever, that is
> why I believe we could deprecate it.
>
> I remember the idea of injecting allocator into containers, I do not
> remember why it died (was it memory expensive?). From api perspective it
> would be a better solution.
I don't remember if we've ever discussed that.
I am, in fact, quite opposed to it. I want to replace our current allocator
with a slice allocator whenever possible.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
More information about the Development
mailing list