News for hackers. Stuff that matters.
Re:Writing secure Go code by klabb3 on Monday November 04, 2024 @05:08PM (#42046496)
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.

Re:Writing secure Go code by tptacek on Monday November 04, 2024 @05:14PM (#42046559)
Ordinary non-race-checked Go code is memory-safe in the sense that we mean it in the field of software security.
Re:Writing secure Go code by oasisaimlessly on Tuesday November 05, 2024 @04:35PM (#42055380)
"We"? Do you have a mouse in your pocket?