On Wednesday, 28 January 2015 at 14:41:09 UTC, Dicebot wrote:
And with no plans to deprecate old syntax even more
inconsistency had been introduced.
When the problem arises, then.
Same goes for possible introduction of new attributes - if
syntax for those and UDA is identical, it can break code same
as introducing new keywords.
Same for any symbol. Do you have a solution?
I don't see any _vision_ behind the change, just moving bits
around.
It is not well-thought.
@pure, @nothrow and @return are relatively obscure attributes, so
if they change, it should cause minor commotion. If you want to
overhaul everything, you can propose a DIP.
