I Avoid Async/Await

Re:I Avoid Async/Await by zkldi on Saturday April 16, 2022 @10:31AM (#31052629)

I don't think it's a good practice, atleast if you have typescript jn your stack. It's redundant and wraps the promise in another promise.

[ Parent | on HN ]

Re:I Avoid Async/Await by eurasiantiger on Saturday April 16, 2022 @11:14AM (#31052947)

IIRC that doesn’t actually happen if a native Promise is returned.

[ Parent | on HN ]

Re:I Avoid Async/Await by eyelidlessness on Saturday April 16, 2022 @12:33PM (#31053727)

It does, but only if you also add a redundant await. Which I still do, even in TypeScript, unless there’s a compelling performance reason not to. I disagree with the article overall, but I do agree that making asynchrony as explicit as possible is a good idea. Otherwise you end up with code like:

  async function foo(bar) {
    // ...
  }

  function nonObviousAsyncFn() {
    // ...
    return foo(quux);
  }

Explicit return types would help, but most people don’t write them unless they’re forced by a linter.

[ Parent | on HN ]

Re:I Avoid Async/Await by Aeolun on Sunday April 17, 2022 @06:13AM (#31059806)

This would still return a promise for both functions. My IDE at least is really obvious about what happens.

[ Parent | on HN ]

Re:I Avoid Async/Await by eurasiantiger on Sunday April 17, 2022 @03:24AM (#31059155)

Yes, this is a common anti-pattern

    return await foo();

[ Parent | on HN ]