Mention @everywhere in pmap documentation #12300
Merged
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
I noticed that `pmap(f,lsts)` only works for me if `f` is defined with `@everywhere`, so I added that note to the documentation for `pmap`. Is this correct, or is `@everywhere` not going to be required in the future?
|
Recently bite by this too. I think the key is that it has to be available everywhere and |
yuyichao
added
docs
|
Good idea. I added the link. How does this look? |
|
lgtm |
jakebolewski
added a commit
that referenced
this pull request
Jul 27, 2015
Mention @Everywhere in pmap documentation
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.
I noticed that
pmap(f,lsts)only works for me iffis defined with@everywhere, so I added that note to the documentation forpmap. Is this correct, or is@everywherenot going to be required in the future?