Re:Writing secure Go code
by danielheath on Tuesday November 05, 2024 @01:00AM
(#42048952)
Go lets you use `unsafe.Pointer` (or indeed, assembly intrinsics) if you really want to, but those are certainly not used "ordinarily".
[ Parent
| on HN ]
Re:Writing secure Go code
by tsimionescu on Tuesday November 05, 2024 @03:11AM
(#42049588)
It's not just about that. Data races can expose an object in a state that was never written from any thread in Go, potentially corrupting even internal details not exposed. Simply writing a struct value from two different threads can expose this.