DMD 1.029 and 2.013 releases

[Walter Bright]

Steven Schveighoffer wrote:
> You can sort of work around it by wrapping the previously volatile statement 
> in a function, but it seems like having volatile doesn't really hurt 
> anything.  I'm curious to know why it was so bad that it was worth 
> removing...

Because after listening in while experts debated how to do write 
multithreaded code safely, it became pretty clear that the chances of 
using volatile statements correctly is very small, even for experts. 
It's the wrong approach.