Deprecated Library Functions / Methods

[Walter Bright]

On 12/1/2012 4:47 AM, bearophile wrote:
> In another thread people are discussion a solution that will help you, a
> "Stable D", updated only once in a time, like every 6-8-12 months, that
> has no know regressions and where only nonbreaking changes are allowed
> (here Phobos modules deprecations are probably to be intended as
> breaking changes).

I don't view the stable/dev branches of D as being a license to break 
existing code. Breaking code in the dev version should only be done if 
there's a very large benefit/cost ratio.

Not for bikeshedding reasons, and not if there's a way we can keep the 
old behavior around.