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

[via Digitalmars-d-bugs]

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

Jonathan M Davis <jmdavisProg at gmx.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jmdavisProg at gmx.com

--- Comment #4 from Jonathan M Davis <jmdavisProg at gmx.com> ---
I'm very much against this because then it's possible to have both nothrow and
@nothrow in code (and the same for the others), and that's just going to create
confusion. Right now at least, it's clear when you get it wrong, because you
get a compilation error, but if we allowed this, then many users won't know the
difference between the two, and confusion and questions will ensue. I really
think that they should be one way or the other and not both.

In addition, it's not like this makes everything consistent, because attributes
like static or const wouldn't ever have @ on them. If this change were forced,
all it would do is move some of the attributes from keywords to the @ side - it
wouldn't actually make them all consistent- and making it so that you _can_
mark some of them with @ but don't have to is just going to increase confusion
and inconsistencies between programs. This isn't just not worth it IMHO; it's
detrimental.

--