git.ralfj.de Git - web.git/history - personal/_posts/2025-07-24-memory-safety.md

]> git.ralfj.de Git - web.git/history - personal/_posts/2025-07-24-memory-safety.md

2025-07-26	Ralf Jung	links for the Go folk's take on this, and wording impro...	blob \| commitdiff \| raw
2025-07-26	Ralf Jung	emphasize that this is not a Go panic	blob \| commitdiff \| raw \| diff to current
2025-07-25	Ralf Jung	avoid vague 'reasonably', mention memory corruption	blob \| commitdiff \| raw \| diff to current
2025-07-25	Ralf Jung	link to another website saying Go is memory-safe	blob \| commitdiff \| raw \| diff to current
2025-07-25	Ralf Jung	mention int2ptr cast and multi-word atomics	blob \| commitdiff \| raw \| diff to current
2025-07-25	Ralf Jung	make tradeoff point more clear	blob \| commitdiff \| raw \| diff to current
2025-07-25	Ralf Jung	better reddit link	blob \| commitdiff \| raw \| diff to current
2025-07-24	Ralf Jung	link more directly to anecdotal evidence (albeit with...	blob \| commitdiff \| raw \| diff to current
2025-07-24	Ralf Jung	java-safe wording	blob \| commitdiff \| raw \| diff to current
2025-07-24	Ralf Jung	link to dtolnay's discussion of the issue	blob \| commitdiff \| raw \| diff to current
2025-07-24	Ralf Jung	mention proving	blob \| commitdiff \| raw \| diff to current
2025-07-24	Ralf Jung	mention Go concurrency expectations	blob \| commitdiff \| raw \| diff to current
2025-07-24	Ralf Jung	mention 'strict concurrency'	blob \| commitdiff \| raw \| diff to current
2025-07-24	Ralf Jung	add memory-safety post	blob \| commitdiff \| raw \| diff to current

sources for my website