Skip to content

Resolving should lock to first call, even for thenable #22

Description

@glebec

See promises-aplus/promises-spec#246. In short, if it is possible to call resolve multiple times, the first resolve should win — even if it's a pending thenable (non-trusted promise), and subsequent calls are made with immediately-available synchronous values. Potential currently fails this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions