[Development] qsizetype and classes working with QStrings or QList

[Thiago Macieira]

On Monday, 24 August 2020 22:24:52 PDT Philippe wrote:
> > Do we need models with more than 2 billion rows or columns?
> 
> More than we need in-memory containers with more than 2 billion entries,
> no?

More? We see a lot of data processing bumping up to gigabyte levels. 
Containers with more than 2 billion items are rare, but I see it happening for 
QByteArray and QString at least.

But how about models? This is an honest question. Does it make sense for 
tables and lists that big? Note that an item *view* has a purpose of being 
viewed, so how does one display such a huge list, tree or table?

> For instance, one could wish to display in a list view, the contents of
> a file with more than 2 billions "entries".
> 
> But then there would be the need to make QAbstractSlider be able to
> handle 64 bit quantities too.

How does that make a good UX?

On an 8k resolution (7680 × 4320), each vertical pixel would represent half a 
million entries.

I'm not questioning the existence of data sets of more than 2 billion entries. 
Those exist. I'm asking how one can make a UX that requires more than 2 
billion rows or columns.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel DPG Cloud Engineering