Hi, On Wed, Feb 15, 2017 at 8:35 PM, Stanislav Malyshev <smalys...@gmail.com> wrote:
> Hi! > > > I can't speak for others, but for me, it's simply because there's no > > reason to do it (remove it), while there may/might be a reason to > > keep it going forward. Keeping it comes at zero cost, and if we ever > > Same here. I just don't see what is improved by this removal. To me, > it's just disruption (admittedly to a small code base, but still) > without any upside. > > While that's an understandable argument, what happens if we flip it? Is there any benefit to keeping it? If it currently does nothing, and the only reason for keeping it is that it may do something in the future ... Well, there will be side-effects to any code that does use it today. In other words, it's supposed to be providing forward compatibility, but any attempt to actually utilize it may only result in a BC *break*. It's not a function or class name, so nothing benefits from reserving it either ... or am I missing something? Cheers, Andrey.
