Re:Having fun with Go's nil, interfaces and errors
by aikah on Saturday September 17, 2016 @06:34PM
(#12522870)
The worse is not, that. I think the worse is that, unlike Java, a race condition in Go has a totally undefined behavior that can corrupt the memory of the entire system your Go app is running on. You can effectively shut down your computer with a race condition in a Go program, and it actually happened to me many times on Windows, with 3rd party Go tools that didn't handle concurrency carefully. Go concurrency is truly unsafe, C style.
[ Parent
| on HN ]
Re:Having fun with Go's nil, interfaces and errors
by mappu on Saturday September 17, 2016 @07:29PM
(#12523078)
This shouldn't happen on any kernel with memory protection. Userspace corruption, sure, but shutting down the computer is unrealistic unless you are running Go code on Windows 98 or classic Mac OS.