@fasterthanlime Ostensibly, this is also one of C's chief issues. It's not simple; it just took the hard bits and says
"Go Fuck Yourself"
every time you want to try to address them in any meaningful fashion. We've fixed some of that in recent versions, but like... it's a running theme that we either just paper over complexity, or -- in the worst case -- shove all that complexity raw into the user's hands and tell them to figure it the hell out themselves. And it's brutal and often not helpful because a lot of that complexity comes from implementation-defined or undefined/unspecified characteristics that are under-documented or not at all documented.
@thephd @fasterthanlime
I'm having fun lately discussing things that C and C++ and LLVM never even fucking tried to handle in a consistent way but we're probably going to have to because we don't want to just gloss over things that matter in, say
proofs of soundness of concurrent operations?
the C++ memory model is effectively incomplete when held up against things programmers actually write.