Editorial: Use abstract closures in Promise static methods
#2588
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for the PR. I'm not totally convinced this is an improvement, which is why I did not convert these as part of #2439. We can see what the other editors think, though. |
|
Thanks for the PR, @ExE-Boss. We discussed this on the editor call, and none of us thought it was a strict improvement. So erring on the side of less churn, we're going to keep the current forms for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Refs: #2439
I left
CreateResolvingFunctionsalone because the Promise Resolve Functions algorithm steps are rather long compared toCreateResolvingFunctionsthat has been converted to use Abstract Closures, and I didn’t want to only convert it halfway.