You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 26, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Jan 26, 2022. It is now read-only.
@bterlson@michaelficarra all major browsers has implemented these features. test262 already have tests (flat, flatMap). It seems that proposal needs just PR to ecma262 to become ES2019
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.
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 :)
Reacted by Jordan Harband, Sergey Rubanov, Sasha Chudesnov, Sathya Gunasekaran, Steven, Michał Gołębiowski-Owczarek and Diogo Korok
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.
Reacted by Steven, Till Schneidereit, Sergey Rubanov, Jordan Harband, Igor Ovsiannikov, Thom and Michał Gołębiowski-Owczarek
Reacted by Sergey Rubanov, Jordan Harband, Michał Gołębiowski-Owczarek and Diogo Korok
Activity
keithamus commentedon Jul 27, 2018
ChakraCore issue chakra-core/ChakraCore#5543
chicoxyzzy commentedon Aug 8, 2018
ChakraCore PR chakra-core/ChakraCore#5573
chicoxyzzy commentedon Aug 21, 2018
@bterlson @michaelficarra all major browsers has implemented these features. test262 already have tests (flat, flatMap). It seems that proposal needs just PR to ecma262 to become ES2019
ljharb commentedon Aug 21, 2018
It’d also need committee consensus.
chicoxyzzy commentedon Aug 21, 2018
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
ljharb commentedon Aug 21, 2018
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.
chicoxyzzy commentedon Aug 21, 2018
Oh. I though that by consensus you mean something like approvement from committee. That unshipping compatibility rule makes sense to me.
ljharb commentedon Aug 21, 2018
Yes, the committee needs to officially approve stage 4 as well.
chicoxyzzy commentedon Aug 21, 2018
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
ljharb commentedon Aug 21, 2018
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.
tschneidereit commentedon Aug 21, 2018
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 :)
michaelficarra commentedon Aug 21, 2018
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.