A rationale for pure nothrow ---> @pure @nothrow (and nothing else changes)

[Robert Clipsham]

On 28/02/10 15:40, Leandro Lucarella wrote:
> I'm not against this, I'm against weird ad-hoc rules to justify it =)

[A few years down the road, D2 is more popular, more code is becoming 
available for it, more programs are being written in it]

Novice: There's just one thing I don't understand, why is XXX an 
attribute and YYY not? Is there any rule for what's an attribute and 
what isn't?

[Situation A]
Experienced D User: There's no rule for it, you've just gotta learn 
which are attributes and which aren't.

[Situation B]
EDU: Everything you expect to be an attribute is, with a couple of 
exceptions for historical reasons, such as <list>.

[Situation C]
EDU: There's a rule for it, you can find it at http://.../, but the 
general rule is CCCC.

----

If we can come up with some ad-hoc rule, even if it's quite complicated 
I think it'd be better than nothing. It's too late to sort things out 
properly at this point, but if we can get some sort of a rule it'd help 
when deciding what should be an attribute for D3 and what shouldn't. If 
we leave ourselves without a rule now it's gonna get even harder to come 
up with even an ad-hoc rule.