3 ms·

I'm not familiar with the JS proposal process. Is this likely to become an official feature now that it's been proposed? If so what's the usual timeline of that

I'm not familiar with the JS proposal process. Is this likely to become an official feature now that it's been proposed? If so what's the usual timeline of that look like? I would love to have this feature ASAP in the browser and/or Node.js and am eager to find out when that will be possible.

Axnyff 8y ago
This should help you: http://2ality.com/2015/11/tc39-process.html http://2ality.com/2015/11/tc39-process.html Basically, it's just a proposition for the moment, there's no telling if that's gonna be in the language or not. It's only at stage 2 that it is likely that the feature will be added in the language.
simlevesque 8y ago
Someone will surely do a Babel plugin to use the syntax allowing you to try it before it becomes an official feature.
- maxmcd 8y ago
  Linked in the readme: https://github.com/babel/babel/pull/7633 https://github.com/babel/babel/pull/7633
- Already__Taken 8y ago
  It's at the bottom of the proposal https://github.com/babel/babel/pull/7633 https://github.com/babel/babel/pull/7633
WorldMaker 8y ago
Right now this says it is a Stage 0 proposal, or "Strawman". It's to see if there is interest in the committee to pursue it. So it's hard to tell the likelihood if it will show up in browsers/Node just yet. The TC39 process: https://tc39.github.io/process-document/ https://tc39.github.io/process-document/
soccergee 8y ago
Yeah, I think that's essentially the idea. However the longer part is getting the support native in the browsers. Tools like babel will most likely provide some form of support before the browser does.
habitue 8y ago
This is a Stage 0 proposal. Basically it means somebody with a connection to the TC39 (the committee in charge of the JavaScript standard) has thought this was a good enough idea to put together into a proposal. In terms of chances of standardization, that's a step up from "Hey, I have a great idea", buy there are plenty of Stage 0 proposals that go nowhere because they lose steam. I think the metric they look for is who is using the Babel plugin for it. If people are doing that, then they it has a better shot of progressing. Stage 4 is the "this is getting standardized next time" stage
- pjmlp 8y ago
  Even Stage 4 isn't granted it will end up on the standard, some proposals have died on Stage 4.
  - shados 8y ago
    Any example? Since stage 3 is roughly "request for implementers", and Stage 4 requires 2 real world implementations and essentially mean "will be part of the standard in the next wave". The closest thing I can think of is ES6 modules, because the module loader spec wasn't finished, but the syntax still lived on. Now, stuff getting kicked down from Stage 3, that has happened.
    - pjmlp 8y ago
      I was wrong, on my mind I was thinking SIMD has been dropped during stage 4.

Axnyff 8y ago

This should help you: http://2ality.com/2015/11/tc39-process.html http://2ality.com/2015/11/tc39-process.html Basically, it's just a proposition for the moment, there's no telling if that's gonna be in the language or not. It's only at stage 2 that it is likely that the feature will be added in the language.

simlevesque 8y ago

Someone will surely do a Babel plugin to use the syntax allowing you to try it before it becomes an official feature.

maxmcd 8y ago
Linked in the readme: https://github.com/babel/babel/pull/7633 https://github.com/babel/babel/pull/7633
Already__Taken 8y ago
It's at the bottom of the proposal https://github.com/babel/babel/pull/7633 https://github.com/babel/babel/pull/7633

WorldMaker 8y ago

Right now this says it is a Stage 0 proposal, or "Strawman". It's to see if there is interest in the committee to pursue it. So it's hard to tell the likelihood if it will show up in browsers/Node just yet. The TC39 process: https://tc39.github.io/process-document/ https://tc39.github.io/process-document/

soccergee 8y ago

Yeah, I think that's essentially the idea. However the longer part is getting the support native in the browsers. Tools like babel will most likely provide some form of support before the browser does.

habitue 8y ago

This is a Stage 0 proposal. Basically it means somebody with a connection to the TC39 (the committee in charge of the JavaScript standard) has thought this was a good enough idea to put together into a proposal. In terms of chances of standardization, that's a step up from "Hey, I have a great idea", buy there are plenty of Stage 0 proposals that go nowhere because they lose steam. I think the metric they look for is who is using the Babel plugin for it. If people are doing that, then they it has a better shot of progressing. Stage 4 is the "this is getting standardized next time" stage

pjmlp 8y ago
Even Stage 4 isn't granted it will end up on the standard, some proposals have died on Stage 4.
- shados 8y ago
  Any example? Since stage 3 is roughly "request for implementers", and Stage 4 requires 2 real world implementations and essentially mean "will be part of the standard in the next wave". The closest thing I can think of is ES6 modules, because the module loader spec wasn't finished, but the syntax still lived on. Now, stuff getting kicked down from Stage 3, that has happened.
  - pjmlp 8y ago
    I was wrong, on my mind I was thinking SIMD has been dropped during stage 4.