Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

To add to this: the built in go race detector is very good at catching data races. It’s a runtime, but I’ve never had a race that couldn’t be reproduced in the race detector trivially.

But yes, in theory Go has a memory safety problem because of it. In practice though, it’s that people don’t use the race detector, which is ridiculously easy to do.



Ordinary non-race-checked Go code is memory-safe in the sense that we mean it in the field of software security.


"We"? Do you have a mouse in your pocket?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: