> Sent: Friday, February 03, 2017 at 11:48 AM > From: "Konstantin Tokarev" <annu...@yandex.ru> > To: "Jason H" <jh...@gmx.com>, "Samuel Gaist" <samuel.ga...@edeltech.ch> > Cc: "interestqt-project.org" <interest@qt-project.org> > Subject: Re: [Interest] QML async/await support? > > > > 03.02.2017, 19:43, "Jason H" <jh...@gmx.com>: > >> 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. > > V4 does not support ES2015, and you are referring to ES2017 specification. > Doesn't make very much sense.
I'm not looking for spec completeness, I'm looking for features. Though I'd argue that having out-of-spec JS would be a bad idea overall since it splits the JS code base. _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
