On Monday, 25 November 2019 13:59:28 PST Arnaud Clère wrote:
> Hi Thiago,
>
> Regarding the last part:
> - 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 latter
How many do s
-Original Message-
From: Thiago Macieira
>
> My point is that I can see the value in providing a single method whereby our
> and users' types
> can provide a descriptive format for their serialisation, regardless what the
> serialisation backend is.
> That way, a single method could be u
On Sunday, 24 November 2019 12:18:07 PST Arnaud Clère wrote:
> - Thiago recognized that this kind of API would be valuable to Qt users but
> at least the naming is problematic, so he should provide feedback before it
> can be pushed to and reviewed on gerrit
My point is that I can see the value in
Hi all,
Thank you for the discussions at QtCS19!
The notes regarding the session on serialization are on the wiki:
https://wiki.qt.io/Rethinking_serialization_for_Qt6
To summarize:
- Although it seemed strange to many people, it is possible to provide an
API so that a single T::zap() method can r
