C# - Is "volatile" really needed as a keyword?

Viewed 1543

As I read deeper and deeper into the meaning of the volatile keyword, I keep saying to myself "this is way into implementation, this should not be a part of a high level programming language".
I mean, the fact that CPUs cache the data should be interesting for the JIT compiler, not to the C# programmer.

A considerable alternative might be an attribute (say, VolatileAttribute).

What do you think?

5 Answers
Related