This sort of follows on from the EINTR discussion a while back, but was prompted by a claim in the gophers #general slack channel that "the Go scheduler will actively try to interrupt CGO calls that take too long"[1].
This doesn't seem right to me, but I wanted to confirm from people who know (also is there any documentation about the behaviour of the new pre-emptive scheduler?). thanks Dan [1] https://gophers.slack.com/archives/C0UKS8V9S/p1583511112030900?thread_ts=1583487810.024900&cid=C0UKS8V9S -- 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/5c06438bd12fe6fa8a6da49170b1fb024ca7422b.camel%40kortschak.io.
