-Original Message-
From: Thiago Macieira
>
> Would it make sense if this API were not in QtCore?
> Then we could give it a try and see how many people think it's useful, what
> its pitfalls are, etc.
Yes, it is possible and it perfectly makes sense. It does not have to
wait for Qt6 too.
On Tuesday, 26 November 2019 23:13:46 PST Arnaud Clère wrote:
> -Original Message-
> From: Thiago Macieira
>
> > > value.meta(qmColumns,"key,value").bind(map.iterator())
> >
> > I really, REALLY do not like this line.
>
> I was going to explain all meta(...) were never required, but wel
-Original Message-
From: Thiago Macieira
> > value.meta(qmColumns,"key,value").bind(map.iterator())
>
> I really, REALLY do not like this line.
I was going to explain all meta(...) were never required, but well,
you have pretty well summarized your arguments so I will just stop
wasting o
On Tuesday, 26 November 2019 06:50:28 PST Arnaud Clère wrote:
> value.meta(qmColumns,"key,value").bind(map.iterator())
I really, REALLY do not like this line.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
Now, this is the discussion I was hoping for at QtCS :-)
> -Original Message-
> From: Thiago Macieira
>
> > - it is frequent to have to save/load our types and then send/receive
> > them to some server/device using, say QSettings/QJsonDocument for the
> > first and JSON/CBOR for the latte
