Does anyone understand how to use "shared" types with concurrency send/receive functions?

[Kagamin via Digitalmars-d-learn]

On Monday, 14 August 2017 at 20:13:28 UTC, Arek wrote:
> If I can ensure the uniqueness of the object, there is no need 
> to "share" it or synchronize the access.

You use manually managed multithreading, that's why you need 
shared. And because compiler can't verify uniqueness, you are 
requested to do it manually by casting.