&gt; but I don&#x27;t think Rust&#x27;s concurrency primitives are either given the (very real, very bad) possibility of deadlock.<p>OK. Then I don&#x27;t know what to say. An infinite loop is a deadlock. Unless you have a programming language that can guarantee termination, you can&#x27;t prevent deadlocks statically.<p>So yes, I think a brief marketing pitch of &quot;safe and easy concurrency&quot; is totally appropriate given the domain Rust is shooting for. In fact, it is one of Rust&#x27;s strengths, so to not advertise it as such would be quite odd.<p>&gt; Which are a good start, but only a partial solution without coroutines (and the other additions you mentioned).<p>OK. But you said &quot;And because Rust doesn&#x27;t provide higher level concurrency tools than threads and mutexes&quot; which just isn&#x27;t true. I&#x27;m trying to clear up what it is Rust <i>does</i> have. I&#x27;m not saying it has everything. Writing software takes time.