On 4 February 2017 at 00:42, Jason H <jh...@gmx.com> wrote: > > > > Sent: Thursday, February 02, 2017 at 3:40 PM > > From: "Samuel Gaist" <samuel.ga...@edeltech.ch> > > To: "Jason H" <jh...@gmx.com> > > Cc: "interestqt-project.org" <interest@qt-project.org> > > Subject: Re: [Interest] QML async/await support? > > > > > > > On 2 Feb 2017, at 18:02, Jason H <jh...@gmx.com> wrote: > > > > > > When will QML get proper async/await support? I'm not using Promises, > since my callback hell is manageable, but I do look forward to async/await. > > > _______________________________________________ > > > Interest mailing list > > > Interest@qt-project.org > > > http://lists.qt-project.org/mailman/listinfo/interest > > > > Hi, > > > > Looking for something like https://github.com/benlau/quickpromise ? > > > Thanks but promises are a fad, created because of a lack of async/await. > Their replacement is async/await. As of July '16, they were committed to > ECMAscript 2017. At the January '17 meeting the final ECMAscript 2017 > featureset was announced whose major features are async/await and shared > mem & atomics. > > The JS community has been using async/await via babel for some time. > Python is also moving to async/await, with 3.5 introducing and 3.6 > completing support for async/await. > > Given that the future is here, that's why I was asking. I think (I'm very > not sure) that V4 would have to be modified for async/await. Given the > relative enthusiasm for async/await I was wondering if it was scheduled for > V4. > > > Upgrade the Javascript engine would take a lot of time. Instead, I think it should just use babel to compile JavaScript code that compatible with v4. That will be much easier.
There has a project called , quickly , is aimed for this purpose. But unfortunately the development is suspended for long time. https://github.com/quickly/quickly
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest