Will Coleda wrote:
I agree that any removed feature should have a deprecation cycle; Here's my pitch for how we've already done that; the list of deprecated features has RTs; the RT listed what was going to have to happen for some time now; This covers us on the deprecation notification. I am willing to be outvoted, however, and have the patch temporarily reverted until post-release, as long as we re-apply it shortly after. I see a related patch from cotto after mine, would need to get that one too.
This ticket has given several months of notice that builtins were being deprecated.
Let's do a quick query of other languages: Is anyone else affected by the change? And, is a quick update to a method call instead of the builtin a workable solution for you?
Overall, I suspect updating any affected languages is less hassle than backing out the patch (that is, I don't expect wide usage), so it's the better path forward.
Allison
