News for hackers. Stuff that matters.
Re:Go 1.16 Release Notes by pansa2 on Tuesday February 16, 2021 @05:54PM (#26159840)
> I have wrapped a large C++ library for Go

How well does it work the other way round - calling Go from C/C++? IIRC when I first looked into doing that, it wasn’t really possible - only threads that were started by Go could run Go code. In particular, `main` had to be in Go and couldn’t be in C++. Does that restriction still apply?

Re:Go 1.16 Release Notes by _ph_ on Tuesday February 16, 2021 @06:03PM (#26159952)
I have created shared libraries with Go which can be called from C, no problems. Those shared libraries can start their own goroutines quite fine and can call back into the C application. Usually it is a good idea to call back into the C application from the thread the Go function called from C was running.
Re:Go 1.16 Release Notes by eptcyka on Tuesday February 16, 2021 @06:30PM (#26160224)
Is there a way to bind a goroutine to a specific thread? Afaik, all C interop goes through a global lock because the runtime is weird.
Re:Go 1.16 Release Notes by pansa2 on Tuesday February 16, 2021 @06:35PM (#26160271)