Skip to content

Disallow empty binding patterns #5352

Closed

Description

It's currently being discussed whether or not an empty binding pattern should be an early error.

See tc39/ecma262#97

Activity

  1. added
    BugA bug in TypeScript
    Breaking ChangeWould introduce errors in existing code
    ES6Relates to the ES6 Spec
    and removed
    BugA bug in TypeScript
    on Oct 21, 2015
  2. RyanCavanaugh commented on Feb 1, 2016

    @RyanCavanaugh
    Member

    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.

  3. DanielRosenwasser commented on Feb 1, 2016

    @DanielRosenwasser
    MemberAuthor

    Consider #5586 while discussing this.

  4. added
    By DesignDeprecated - use "Working as Intended" or "Design Limitation" instead
    and removed
    Breaking ChangeWould introduce errors in existing code
    SuggestionAn idea for TypeScript
    on Feb 1, 2016
  5. RyanCavanaugh commented on Feb 1, 2016

    @RyanCavanaugh
    Member

    If ES6 was willing to justify this, we're OK with it too.

  6. locked and limited conversation to collaborators on Jun 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    By DesignDeprecated - use "Working as Intended" or "Design Limitation" insteadES6Relates to the ES6 Spec

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions