Just implement generics already. Sheesh. https://github.com/google/gvisor/blob/master/tools/go_generics/generics.go …
I should also mention that the starvation issue has been discussed a lot, and years ago there was a rough consensus to spin up more threads to prevent starvation. Not sure if that has changed. BTW, Go has the same issue with cgo threads and uses this technique.
-
-
That kind of lint would be defeated by any abstraction boundary that has a mutex internally. Unless you track "could block" at the type-system level. Also, there are lots of things that block thread pools, mutexes are just one example.
-
Go certainly has issues with its FFI (performance being another). But seems like a difference of magnitude; percentage of CGo-using Go programs is probably under 15%. Percentage of programs that ever make use of both blocking APIs and some sort of IO is closer to 100%.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.