Document behavior of the default hash function of async.memoize #631
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
added 3 commits
May 9, 2013 12:28
… stack if the iterator function sometimes invokes the callback directly with 'return callback();'
aearly
added a commit
that referenced
this pull request
May 19, 2015
Document behavior of the default hash function of async.memoize
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.
This is my understanding of the default hash function of async.memoize, which isn't currently documented. Hopefully it will be accepted or corrected. Either way, I learn if I'm right!
There are three commits because github can't quite figure out I backed out an older pull request of mine, but the diff is clean.