Because it supports asynchronous messaging too? As if CSP were some concept that emerged fully formed from Tony Hoare's head like Athena from Zeus?
I'm sorry you see dichotomies where others see dualities.
The tone of your previous comment made me feel that this thread is going in an unproductive direction, so I'll stop here.
Perhaps you should try to be more informed about Rust before you try to have an argument about it in the future!
AFAIK, rust also doesn't allow selecting between a send and receive on channels. It only allows selecting over a set of receivers and even there it doesn't offer something like the default clause of Go's select statement.
Perhaps you should try to read my comments in their entirety before making accusations.
Yes I missed sync_channel, but if that is all CSP was, Java does CSP too. It has Threads and SynchronousQueue exactly like rust 1.0 will.
This is where I again point out that neither Java nor Go ensure that state sent over channels is actually isolated, and both allow data races.
With Rust that is not the case. You have true isolation (unless you explicitly opt not to)
However, even if that exists, rust's concurrency doesn't follow CSP as much as go's. Like I mentioned in my previous comment, it doesn't have a way to do everything the select statement in go does. This is not necessarily a bad thing, but rust definitely doesn't share the same concurrency concepts as go. It offers everything that Java/C++ does along with data race protection.
Speaking of data race protection, the current type system rejects a lot of very common "non-racy" code too. There is work in progress to address some of them and may be most of them will be addressed eventually.