Moving towards D2 2.061 (and D1 1.076)

[Walter Bright]

On 12/13/2012 4:05 PM, deadalnix wrote:
> You have to understand that this isn't their need that is important here. They
> need stuff that we mostly all need, so I tend to agree. The fact is that you
> unilaterally decide to give that priority, when we are not even aware of them or
> of their needs. And that is the problem.

Remedy only recently allowed me to talk about it.


> Isn't it preferable to help them to migrate to the new syntax rather than
> bringing everybody in the same boat ? The feature hasn't been released, so I'm
> pretty sure most D actor don't have a lot of them in their codebase, which make
> the support into the transition easy.
>
> Introducing new deprecated feature into a release seems completely backward to
> me, and reading other comment, it seems that I'm not the only one. We should
> consider other solutions before sticking to that one. And you have to work with
> D community on that one, or you'll loose it.

It was the D community that selected the @(attribute) syntax, and the overall 
design was based on extensive public discussion threads here about it.