util: attach return value to promisified functions #28529
Closed
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.
Some functions that perform asynchronous tasks and
take a callback also return a synchronous result which
can be used in the same tick. Previously util.promisify
was discarding the return value.
While #28325 solved the problem for some specific functions, the general problem for user-defined functions remained. It seems that not so rare practice is to return a useful value along with scheduling asynchronous actions in a function which takes a callback.
Documentation is not added yet. I would like to hear some feedback first regarding whether this change is a good change (or maybe some better suggestions for the symbol name?).
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes