On 8/14/2016 2:12 PM, Dicebot wrote:
On 08/14/2016 10:50 PM, Walter Bright wrote:
Hmm, but we've always done warning => deprecation => error
Yes, and it was a major disaster because most sensible projects compile
with warnings as errors enabled (it is also the default in dub) and thus
putting a warning breaks a many more times more code than putting a
deprecation. We have already talked that through before with Martin and
it seemed acknowledged that pattern has to be changed to "deprecation ->
(optional warning) -> error".
Ok, that makes sense. Thanks for the explanation!
