search

babel / proposals

✍️ Tracking the status of Babel's implementation of TC39 proposals (may be out of date)
https://github.com/tc39/proposals
433 stars 39 forks source link

new proposal: `await.ops` implemented by custom parser #68

Open JounQin opened 4 years ago

JounQin commented 4 years ago

await.ops proposal

implementation: https://github.com/JounQin/babel-plugin-proposal-await-ops/commit/4cc44f8ad38bc7bfaaa141733cb532ba561e422e

Shall I post a PR to babel repo or this repo first?

JLHwung commented 4 years ago

Yes! PR to the Babel repo is welcome!

nicolo-ribaudo commented 4 years ago

(cc @Jack-Works)

Jack-Works commented 4 years ago

Happy to see this! But the proposal is likely going to change to modify the syntax on the for...of statement instead of await syntax. It also possible to only have the equivalent of await.all in the future.

nicolo-ribaudo commented 4 years ago

If it's going to change that much, we could add a mandatory version: "jul-2020" (the last meeting where it was presented) option, so that we can add a new version in the future.

If you prefer not to have this plugin for know, we can wait implementing it, but we are already using the version option for other unstable proposals.

JLHwung commented 4 years ago

@nicolo-ribaudo I suggest we wait for a while if the proposal is likely to be renamed in the future. For example it may be renamed as await-all if only await.all is supported. In that case we are in a middle ground to face decision whether we should rename @babel/proposal-await-ops to @babel/proposal-await-all.

This is not unprecedented: module-attributes => import-attributes => import-conditions => import-assertions and still TBD. 😄

Holybasil commented 2 years ago

👀

Jack-Works commented 2 years ago

This proposal currently lacks motivation strong enough to move forward. Don't hope too much of progression.