These features become orthogonal when the right primitives are there, and so there's no need for a "system" (other than the language/platform itself). Some of the communication problem is already addressed by other Loom features (https://openjdk.org/jeps/453), and others will be addressed by future ones (like channels).
> BlockingQueue is a kind of channel already, what are you thinking to add?
The main difference between a channel and a BlockingQueue is that a channel can be closed, i.e. it allows one or both sides to signal the other that they're done producing/consuming.
> And to the main point, of course, Java has plenty of thread comrunioation possibilities, Loom just makes threads cheaper.
