Deprecations: Any reason left for warning stage?
Daniel Kozák via Digitalmars-d
digitalmars-d at puremagic.com
Fri Sep 26 14:12:47 PDT 2014
The only one and right solution is print warning message by default
----- Původní zpráva -----
Od:"David Nadlinger via Digitalmars-d" <digitalmars-d at puremagic.com>
Odesláno:26. 9. 2014 18:20
Komu:"digitalmars-d at puremagic.com" <digitalmars-d at puremagic.com>
Předmět:Deprecations: Any reason left for warning stage?
As Walter mentioned in a recent pull request discussion [1], the
first formal deprecation protocol we came up with for language
changes looked something like this:
1. remove from documentation
2. warning
3. deprecation
4. error
(The "remove from documentation" step is a bit questionable, but
that's not my point here.)
However, in the meantime deprecations were changed to be
informational by default. You now need to explicitly need to pass
-de to turn them into errors that halt compilation. Thus, I think
we should simply get rid of the warning step, just like we (de
facto) eliminated the "scheduled for deprecation" stage from the
Phobos process.
Thoughts?
Best,
David
[1]
https://github.com/D-Programming-Language/dmd/pull/4021#issuecomment-56758916
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/digitalmars-d/attachments/20140926/702b745d/attachment.html>
More information about the Digitalmars-d
mailing list