synchronized vs. C volatile

[Kagamin]

SK Wrote:

> So long as code does not attempt a read-modify-write operation, shared
> has the opportunity to do the right thing, namely implement volatile
> semantics.  Cases with volatile read-modify-write would have to be
> split -- awkward, but maybe ok?

D provides good behavior by default (for most common cases). If you want alternative behavior, you can still implement it by, say, casting.
Not D is more targeted for user application development. For kernel development compiler should be modified (gcc is, for example).