[Issue 13388] accept '@' before 'nothrow', 'pure', 'final', 'abstract' and 'override'

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=13388

--- Comment #6 from Jonathan M Davis <jmdavisProg at gmx.com> ---
(In reply to Ketmar Dark from comment #5)

> about 'static': this is not an 'attribute' like 'nothrow', 'cause we can't
> write:
> 
>   void bar () static {}
> 
> (why, btw?)

public, private, etc. are in the same boat:

https://issues.dlang.org/show_bug.cgi?id=12930

The attributes are treated consistently in general, which sucks, and I think
that the placement issues can and should be fixed, but I don't think changing
any of the attributes to @ is even vaguely worth it, especially considering the
resulting code breakage (not to mention, it's very ugly for them all to start
with @ IMHO). Just think of the @ as part of the name, and the inconsistency
goes away anyway, since then you just have some attributes which happen to
start with the same character, just like happens with attributes like private
and public. With that line of thought, complaining about some attributes
starting with @ and some not would be like complaining that some attributes
started with p and some didnt'.

--