Addendum: for the bottom question, I would expect the goroutines launched to be scheduled right after the initial callback/wrapped func returns unless there is a blocking operation in which case the scheduler might run them earlier. I also do not know if the goroutines would run in a given order, I would think it to be potentially random. (in the case multiple goroutines were launched within a callback)
All this before any other callback can be called from js. Is that right? (still unsure of what it entails in terms of synchronization requirements) On Saturday, July 2, 2022 at 3:40:10 PM UTC+2 atd...@gmail.com wrote: > Hi, > > I just have a quick question. > I am using callbacks that run Go code to modify a Go-wasm datastructure. > These callbacks are essentially Wrapped Go Funcs called from js. > > Reading the docs, I've realized that each callback runs in its own > goroutine. > Now, I'm wondering if I should protect access to the datastructure with > mutexes. > > It's a bit unclear here as I think the current implementation guarantees > that each callback fully returns before another one gets processed (because > the event loop is prempted each time a wrapped function gets called until > it returns). Seems to me that callbacks into Go code can only be > sequentially processed(?) > > Also, if I launch a goroutine in one of these wrapped funcs, when would it > be scheduled to run? Before the wrapped func it was launched from returns? > > Many thanks, > > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/7a0b4bf0-ef11-4123-a4e3-13de01217b43n%40googlegroups.com.
