On quarta-feira, 1 de novembro de 2017 05:23:04 PDT Иван Комиссаров wrote:
> Sorry for digging the thread, but how is
> * use qssize_t
> and
> ** Wrapping std::{unordered_}map may be acceptable
> combines?
> std::*map uses size_t in it's API (size, max_size, count, reserve,
> begin(size_type), end(size_type))
Our wrapper API can still use qssize_t.
"Won't that limit the actual maximum size?"
No, not really, since it's already limited to half the full VM space. No
object can be larger than that. Using unsigned is unnecessary.
> And offtop - what about allocators? They would be accesibble for wrappers,
> but not accesible for QVector/QString?
They wouldn't be accessible for wrappers either.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
