https://issues.dlang.org/show_bug.cgi?id=13388
Nick Treleaven <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #31 from Nick Treleaven <[email protected]> --- (In reply to Jonathan M Davis from comment #28) > Regardless, I don't see any way that changing which attributes have @ on > them and which don't is going to make it consistent unless you put @ on all > of them, or you don't put it on any of them. The simplest consistent change would be to have built-in @attributes when they *only affect* functions, not variables. Then we don't need @const or @ref, as they can also affect variables/parameters. We would have @pure, @nothrow, @override, @abstract, @final ('@final class' only affects a class's methods, not variable members). 'return' would not be an attribute, as it can affect parameters. Using this guideline, we only have to change 5 attributes. --
