Update asyncmap docs to clarify order of outputs #54974
Open
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
|
Should this actually be guaranteed, or is this a case of "that's what it happens to do right now"? |
I will have to defer a definitive answer to that question for someone else. I'm basing my PR on the answer to a question I had about this in the julia slack. In any case, clarification either way for what I should expect (or not expect) would be useful to have in the docs. |
|
It should be semantically guaranteed since it is supposed to be like |
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.
small addition to
asyncmapdocstring to clarify that order of output is same as input:I added it to clarify the behavior, especially for new users, and, afaik because it is not consistent across programming languages.
Happy to iterate if there should be updates to doc pages too.