So in various github issues TC39 is reliving 30 years of tail call debates (PTC vs TCO, etc.)
-
-
@awbjs as far as the spec is concerned TCO is "unobservable" therefore JSC does not need to revert it. -
@wycats yes, but ES6 had good reasons for including PTC and removing that from the spec would be a significant regression -
@awbjs I'm not in favor of removal but I am in favor of reality. Implementor revolt is a risk of the pre-ES2016 process. -
@wycats we expected push back from some impls. That's why it's in the spec. Shouldn't consider folding on first such push back. Test of time -
@awbjs that reasoning is a holdover from ES2015 process. I don't think it holds up anymore. But I agree that the consensus DOES exist. -
@awbjs and we should make people work hard to establish a new consensus, not just let them retroactively veto. -
@wycats there is no retroactive veto. Removal from spec requires a new consensus which in this case I doubt is achievable. PTC is part of ES -
@awbjs I agree that it requires a new consensus. I think they're trying to get one :) - 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.