go-async/

[utterances-bot]

Retrofitting Async/Await in Go 1.18 | CS Grinding

It is idiomatic to use channels in Go, so why do we need async/await?

https://csgrinding.xyz/go-async/

[Dragomir-Ivanov]

Are you sure this is correct?

// inside an async function
hello = await GetDataAsIntAsync("hello")
foo = await GetDataAsIntAsync("hello")

This will execute the call synchronously.

How about:
hello = GetDataAsIntAsync("hello")
foo = GetDataAsIntAsync("hello")

hello_res = await hello
foo_res = await foo

[ChayimFriedman2]

@Dragomir-Ivanov Promise.all():

const [hello, foo] = await Promise.all([GetDataAsIntAsync("hello"), GetDataAsIntAsync("hello")]);

[Dragomir-Ivanov]

@ChayimFriedman2 Yes, that is little more complex analog to my proposal.
In any case, the code in the article is misleading.

[luqmansen]

I believe we have errgroup for more idiomatic error handling

[bobfang1992]

Are you sure this is correct?

// inside an async function hello = await GetDataAsIntAsync("hello") foo = await GetDataAsIntAsync("hello")

This will execute the call synchronously.

How about: hello = GetDataAsIntAsync("hello") foo = GetDataAsIntAsync("hello")

hello_res = await hello foo_res = await foo

yes, you are right. I will update this later. Thanks!

[jamestrandung]

You should take a drink and forget about that async repo like bad memories from your ex and start using mine :P => https://github.com/jamestrandung/go-concurrency

I reworked the async library from my company to fully support generics and made major enhancements & 10x performance improvement to a feature.

The old version is being used inside my company to serve millions of requests daily at scale. Think about what you can do with mine :).

[bobfang1992]

@jamestrandung sure thanks for the info will take a look.