I found some existing discussion on this topic: https://github.com/golang/go/issues/14163
Not sure I fully understand the reasoning there. If there is a better way forward that doesn't involve adding a controversial function to the scheduling package, I'm all ears. On Saturday, December 14, 2019 at 11:54:26 AM UTC-8, Alex Buchanan wrote: > > Would it be reasonable to make a Go proposal that adds something like > runtime.MainThread(), which would cause the calling goroutine to only ever > be scheduled on the main thread? Unlike runtime.LockOSThread, it would not > need to prevent other goroutines from running on the main thread (I think). > -- 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/2870c84f-2918-4f9d-a456-01fb3d503941%40googlegroups.com.
