[dmd-internals] Regarding deprecation of volatile statements

[Martin Nowak]

> The main problem with shared is that it isn't clear what it is
> supposed to do once it's implemented – we don't even have a memory
> model to _express_ this yet. x86 might be fairly docile in that
> regard, other architectures are not.
>
Java volatile a.k.a. sequential consistency.
I don't think there's much disagreement about this.
The good thing about shared is that it already fully works in conjunction  
with core.atomic.