On 05/11/2017 10:20 PM, Nick Sabalausky (Abscissa) wrote:
On 05/10/2017 02:28 AM, H. S. Teoh via Digitalmars-d wrote:
I'm on the fence about the former. My current theory is that being
forced to write "proper" code even while refactoring actually helps the
quality of the resulting code.
I find anything too pedantic to be an outright error will *seriously*
get in my way and break my workflow on the task at hand when I'm dealing
with refactoring, debugging, playing around with an idea, etc., if I'm
required to compulsively "clean them all up" at every little step along
the way
Another thing to keep in mind is that deprecations are nothing more than
a special type of warning. If code must be be either "error" or
"non-error" with no in-between, then that rules out deprecations. They
would be forced to either become fatal errors (thus defeating the whole
point of keeping an old symbol around marked as deprecated) or go away
entirely.
