Open chicoxyzzy opened 6 years ago
ChakraCore issue https://github.com/Microsoft/ChakraCore/issues/5543
ChakraCore PR https://github.com/Microsoft/ChakraCore/pull/5573
It’d also need committee consensus.
It could be too late for consensus when most of browsers will start to ship it on by default.
While next TC39 meeting will happen on September 25
I’m not sure what you mean by “too late”; stage 4 requires 1-2 shipping implementations minimum (at which point it’s web incompatible to unship it), but there’s no maximum.
Oh. I though that by consensus you mean something like approvement from committee. That unshipping compatibility rule makes sense to me.
Yes, the committee needs to officially approve stage 4 as well.
So if feature won't be approved in the time when it will be shipped in most browsers then it won't go to spec. Though browsers can't unship this feature. Probably other environments will also ship that unspecced feature to make it possible to port code which works on those browsers to their platform. It seems like a big problem. Not sure I understand you correctly though
I think you do; that something can’t be removed isn’t the same thing as that thing being in the spec, because that requires consensus. It’s all in the process document.
This is correct in principle, as the TC39 process requires explicit committee approval for stage advancement. In practice, this is a rubber stamp and an opportunity to do a round of applause in a committee meeting :)
Championing a proposal is (most of the time) a whole lot of work, and that round of applause means a lot. Looking forward to finally putting a bow on this one.