News for hackers. Stuff that matters.
Re:Writing secure Go code by kiitos on Monday November 04, 2024 @05:16PM (#42046568)
Even when a value satisfies these architecture-dependent requirements, the language still does not guarantee atomicity of concurrent reads/writes, and programs which rely on that assumption are buggy.
Re:Writing secure Go code by Yoric on Monday November 04, 2024 @05:36PM (#42046729)
Isn't this part of the Go memory model (https://go.dev/ref/mem)?
Re:Writing secure Go code by kaba0 on Monday November 04, 2024 @05:49PM (#42046866)
Logic bugs != memory safety bugs.

E.g. in java you can mess up your logic with data races, but the racing itself is safe and can never cause the VM to enter an invalid state.