> > > > > > 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. > > Again, Qt's purpose is not create another JS in JS world they reinvent the wheel just because lack of possibility for native development (native in terms of CPU, not OS) Here you dont need this just because you have more efficient tools I've mentioned above
-- Best regards, Vlad
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
