I mean, this explanation makes sense, but after thinking about it a bit, I don't think those are even relevant. I'd wager if one removed all notions of concurr

I mean, this explanation makes sense, but after thinking about it a bit, I don't think those are even relevant. I'd wager if one removed all notions of concurrency from Rust and only left in the `Send` and `Sync` traits (along with borrows, of course), it seems like Rust would still warrant such statements way more. OTOH, saying this about Go due to "memory model and threading primitives" sounds a little bit like describing C++ as a language with "first class functions" because there's `operator()`…