-
Notifications
You must be signed in to change notification settings - Fork 12.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disallow empty binding patterns #5352
Comments
DanielRosenwasser
added
Bug
A bug in TypeScript
Breaking Change
Would introduce errors in existing code
ES6
Relates to the ES6 Spec
In Discussion
Not yet reached consensus
and removed
Bug
A bug in TypeScript
labels
Oct 21, 2015
Note: Outcome in linked bug was to continue to allow empty binding patterns. That said, we should think carefully about how this ought to work in TypeScript since we have more user-side syntactic ambiguity and might want to make this an error. |
Consider #5586 while discussing this. |
RyanCavanaugh
added
By Design
Deprecated - use "Working as Intended" or "Design Limitation" instead
and removed
Breaking Change
Would introduce errors in existing code
In Discussion
Not yet reached consensus
Suggestion
An idea for TypeScript
labels
Feb 1, 2016
If ES6 was willing to justify this, we're OK with it too. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It's currently being discussed whether or not an empty binding pattern should be an early error.
See tc39/ecma262#97
The text was updated successfully, but these errors were encountered: