3 ms·
It also doesn't really make much sense. The Go Language Memory Model page is about memory synchronization, not memory management. This article is about memory
by nulltype 11y ago
It also doesn't really make much sense. The Go Language Memory Model page is about memory synchronization, not memory management. This article is about memory management, not low-level details of when writes and reads are visible across coroutine boundaries.
- copsarebastards 11y agoUgh, seriously? The page says: "If you must read the rest of this document to understand the behavior of your program, you are being too clever. Don't be clever." That's an idiotic thing to say. I don't care if you're saying it about memory synchronization or memory management, it's an idiotic thing to say either way. Redirecting all criticisms of Go and pretending that they don't apply because Go isn't for anything or about anything seems to be the only defense Go users have. Why not, instead of telling us all the things Go isn't for, or all the things Go docs aren't talking about, why don't you actually use a non-shitty language that's actually useful for something.