DIP20: Volatile read/write intrinsics

[Adam D. Ruppe]

On Wednesday, 10 October 2012 at 19:09:34 UTC, deadalnix wrote:
> We discussed it quite a lot already, but I still think volatile 
> must be a qualifier of the memory, and not of the statement.

I barely know anything about this, but couldn't that be done as a 
library type? Something like a smart pointer.

This does bring me to a question though. What if you had:

void foo() {
    volatile_read();
}

foo();
bar();
foo();

Is the call to foo allowed to be reordered? I imagine it has to 
mark the whole call chain upwards as internally volatile too.