First thing is that I’m also sure that no one will change that, I know a little all that
But IMHO my suggestion isn’t so stupid because it could be something more global, you could use it as now and telling in the message that it’s deprecated, instead of
@:deprectated( "Be careful, it will be remove blabla" ) you could have
@:warning( "This field is deprecated, it will be removed" ) or something like that. And in the same time you would be able to throw other “warnings” if you want. It also would change
-D no-deprecated-warnings into
And also when you speak about documentation, what is the difference having
@:warning(...) that could also end in the documentation. I mean, when you read the code or the doc, you see that it’s a warning… Or maybe I haven’t well understood ?
The reason why I suggest something like that, knowing that I can do it with macro, is that using macro, even if you work with a kind of “hub”, it will always be slower that having it in compiler which yet has a “meta processor”.