-
Notifications
You must be signed in to change notification settings - Fork 7
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
isResolved should be named isFulfilled #1
Comments
afaik, |
Nope, that's (almost) settled.
|
We don't currently expose the word |
That difference is because resolving is a verb that can include resolving to another promise's state - although I prefer the term "resolve" here, "fulfill" is indeed correct. This has its roots in E's promises. The spec's intention was for the new Promise executor's arguments to be named "fulfill, reject" - altho the community tends to call them "resolve, reject". |
My point was that the name of the argument is not exposed as either |
Right, but "is resolved" doesn't mean the same thing as "is fulfilled", and |
False. The resolve() argument resolves, not fulfills, e.g. try |
Oops, you are indeed correct. Is the rest of my statement still accurate? |
Yeah |
Changed api and used fulfilled |
AFAIU, resolved means that the promise is fulfilled (has a value) or is chained to another promise (which might not be settled).
The text was updated successfully, but these errors were encountered: