Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Fabrício Matté
    @UltCombo
    Hello world
    Átila Fassina
    @atilafassina
    Hoy!
    Jaydson Gomes
    @jaydson
    Hey
    Russian Rebouças
    @russiann
    Hehehe só brazucas :D
    Jaydson Gomes
    @jaydson
    :+1:
    hacke2
    @hacke2
    哈哈
    Doruk Kutlu
    @d0ruk
    hi there
    can someone explain what the await* operator does in this code?
    Doruk Kutlu
    @d0ruk
    and this?
    const { includes: strIncludes } = core.String.prototype;
    Jaydson Gomes
    @jaydson
    Hi @Norm- , await* is just syntactic sugar for Promise.all
    This is based on the ES7/ES2016 espec
    Doruk Kutlu
    @d0ruk
    Thx
    and i think the second snippet is obj destructuring?
    Jaydson Gomes
    @jaydson
    Yep
    About Async/Await I wrote this Gist https://github.com/jaydson/es7-async
    Doruk Kutlu
    @d0ruk
    Gonna check it out when at a box
    Fabrício Matté
    @UltCombo
    await* was removed from the Async Functions proposal, so I've replaced all await* usages with await Promise.all(). Let's not use await* anymore as that would prevent us from upgrading to Babel 6
    I've also updated our core-js dependency, which gets us rid of ugly constructs like the one that @Norm- quoted in the past. See the diff
    Jaydson Gomes
    @jaydson
    Didn't know about it. Where's the reference?
    Fabrício Matté
    @UltCombo
    oops, sorry for the delay
    I believe await* never made it to the Async Functions proposal's formal spec. text. Babel 6 will also throw an informative error saying that await* was removed from the proposal if you try to compile code containing it.
    Fabrício Matté
    @UltCombo
    await* was described in prose in the proposal's README at some point, but there was no strong motivation to add new syntax for such a simple abstraction. So, I believe it was never properly spec'd in the proposal's spec. text, and removed from the README at some point.
    Fabrício Matté
    @UltCombo
    I've opened #188 to upgrade to Babel 6, but there are still a few Babel bugs that prevent us from upgrading.
    I've linked to the bugs in the PR's comments, so we can track their progress. And, of course, if anyone has enough spare time they can try fixing those Babel bugs too.