Re: [go-nuts] Refactor Asynchronous JS to Go

2022-11-06 Thread Konstantin Khomoutov
On Sun, Nov 06, 2022 at 02:42:52PM +0400, Konstantin Khomoutov wrote: [...] > The chief idea of Go's concurrency is that it's integrated into the language's > code - as opposed to be bolted on in form of a library Sorry, I meant core, of course, not code. -- You received this message because you

Re: [go-nuts] Refactor Asynchronous JS to Go

2022-11-06 Thread Konstantin Khomoutov
On Sun, Nov 06, 2022 at 01:33:59AM +0530, Shubh Karman Singh wrote: > I am refactoring a JS library to Go. I have some questions but I'm not able > to find some concrete answers for this. > 1. What's the idiomatic way to refactor Asynchronous JS APIs to Go? > 2. How to refactor Callbacks from JS t

Re: [go-nuts] Refactor Asynchronous JS to Go

2022-11-05 Thread Kurtis Rader
On Sat, Nov 5, 2022 at 1:58 PM Shubh Karman Singh wrote: > I am refactoring a JS library to Go. I have some questions but I'm not > able to find some concrete answers for this. > 1. What's the idiomatic way to refactor Asynchronous JS APIs to Go? > 2. How to refactor Callbacks from JS to Golang?