Skip to content
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.

Sign up for GitHub

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

Jump to bottom

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

Open
glebec opened this issue Jan 5, 2017 · 0 comments
Open

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

glebec opened this issue Jan 5, 2017 · 0 comments

Comments

@glebec
Copy link
Owner

glebec commented Jan 5, 2017

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@glebec