Even when a value satisfies these architecture-dependent requirements, the langu... | Hacker News

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

		kiitos 9 months ago \| parent \| context \| favorite \| on: Writing secure Go code 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.

Yoric 9 months ago | [–]

Isn't this part of the Go memory model (https://go.dev/ref/mem)?

kaba0 9 months ago | [–]

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.

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