[Development] QVariant container API

Vasily Pupkin shkodindanil.letmework at gmail.com
Tue Mar 31 12:21:36 CEST 2020

If you are going to review the proposed approach I don't mind making a
voice call.
If someone says that this is alright, I will spend time and create a gerrit

On Mon, Mar 23, 2020 at 11:45 AM Ulf Hermann <ulf.hermann at qt.io> wrote:

> Hi,
> We have the same problem in QML: We want to support user-defined
> containers as transparently as possible, with as little "registration"
> overhead as possible. Currently there is a fixed set of pre-defined
> containers you pass between QML and C++ code. See [1] for the relevant
> rant. I've been experimenting with a QML variant of container meta types
> [2], but I haven't gotten very far, yet. I also haven't looked into the
> code suggested by Vasily, yet.
> I'm pretty sure we cannot just remove QSequentialIterable and
> QAssociativeIterable in Qt6. That would be too much of a source
> compatibility break, especially since we haven't deprecated them in Qt5.
> Any solution to container meta types needs to retain those two classes
> as compatibility wrappers.
> [1] https://bugreports.qt.io/browse/QTBUG-71574
> [2] https://codereview.qt-project.org/c/qt/qtdeclarative/+/284171
> Ulf
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> https://lists.qt-project.org/listinfo/development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20200331/fadca852/attachment.html>

More information about the Development mailing list