Skip to content
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.

Remove comma-separated field declaration syntax from this proposal #20

Closed
littledan opened this issue Jul 14, 2017 · 0 comments
Closed

Comments

@littledan
Copy link
Member

littledan commented Jul 14, 2017

Comma-separated field declarations were added relatively recently. Let's split out comma-separated field declarations into a separate proposal to be considered with more time to think over some issues.

Comma-separated field declarations have led to a few sources of confusion, including:

  • In conjunction with decorators, should the decorator apply to only one of them, or all of them? The intention was to apply to all, but some find it ambiguous.
  • Wondering whether we should have trailing commas or some other modified interaction with ASI.
  • Additional complexity and general confusion about the motivation.
  • There is some implementation burden (e.g., in Babel) for the comma-separated declarations, e.g., to ensure the decorator is evaluated once.

None of these are fatal; they would just be reasonable to spend more time thinking about before including in a Stage 3 proposal. My plan is to back these out for now, and work with @wycats to make it possible to propose this separately.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant