"When debugger is active tail calls are disabled."
This sounds like going down a path where running code can change its semantics depending on the debugger being open or not. Would some web pages fail if I have it open? Would the original case from issue 457 still fail because the console is part of the debugger?
And BTW, the more common term for this is "Tail Call Elimination", when it is a language feature rather than a random optimization.
Does this activity from July mean that TCO is going to be shelved for the foreseeable future and/or forever (just a question, not a complaint), or is it just lower on the list relative to other P2 issues? (Or has no decision either way been taken yet, which would be understandable?)
Thanks. -- T.J.
@adamk: Thanks. I wouldn't have expected the Chrome Platform Status page to be where this would be indicated. When I read that (and I had), I figured it mean Chrome was doing nothing until V8 did something.
But again: No active development _now_ or for the foreseeable future? The [proposal for a syntactic flag on tail calls][1] mentioned in that blog post is currently on the list of ["inactive" proposals][2].
Just trying to get a clear picture, if there is one, whether TCO is "dead" in V8 barring movement on that proposal, just delayed with no active development at present, or if that decision hasn't been taken.
Thanks -- T.J.
[1]: https://github.com/tc39/proposal-ptc-syntax
[2]: https://github.com/tc39/proposals/blob/master/inactive-proposals.md
For future reference, V8 indeed uses chromestatus.com to track its work on ECMAScript features.
It's hard to predict the future, but we currently have no plans to do work on tail calls in V8, for the reasons stated in the blog post (and the subsequent inactivity of the syntactic proposal).
So, spec is unimplementable, and all vendors except Apple are silently refusing to either implement it OR change the spec. What should actually happen to move this anywhere?
@adamk: Many thanks! That's very useful. And absolutely, this isn't where discussion should happen. Thanks also for the Chrome Platform Status info. Best -- T.J.
I specifically write functional JavaScript code that relies on proper tails calls. I am stuck using Node 6 to do it. Not implementing this feature is about politics, not technical difficulty. Actually, it's been implemented. This isn't a defect really. It's just a refusal to follow the spec.
Comment 1 by 76821325...@developer.gserviceaccount.com
, Jan 26 2016