DIP62: Volatile type qualifier for unoptimizable variables in embedded programming

[Walter Bright via Digitalmars-d]

On 7/15/2014 2:22 PM, Johannes Pfau wrote:
> The DIP may seem complicated cause it considers overloading,
> transitivity and similar stuff. In practice almost nobody will use
> these features. But if I had not specified them Walters first question
> would have been "How does it interact with overloading" ;-)

You're right that almost nobody would use those features. But they'd have to be 
defined, documented, implemented and tested, like they are in C++. It negatively 
impacts users in that D becomes a larger, more complex language with next to no 
corresponding benefit.

(Just grep for 'shared' in the D source code and see how pervasive it is.)

This is why I propose that peek/poke have a much better cost/benefit ratio.