Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move some spawn related macro docs out of HelpDB #22573

Merged
merged 3 commits into from
Jul 1, 2017
Merged

Conversation

kshyatt
Copy link
Contributor

@kshyatt kshyatt commented Jun 27, 2017

spawn(command) stubbornly remains, I suppose because it's one of those things that's tightly wound in with the code in src/?

@kshyatt kshyatt added docs This change adds or pertains to documentation parallelism Parallel or distributed computation labels Jun 27, 2017
@kshyatt kshyatt requested a review from KristofferC June 27, 2017 16:11
Copy link
Member

@KristofferC KristofferC left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Superficially, LGTM

"""
@spawn

Creates a closure around an expression and runs it on an automatically-chosen process,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps an opportunity to imperative-ize these?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And why not add some examples while we're here...

@@ -30,8 +47,20 @@ end
"""
@spawnat

Accepts two arguments, `p` and an expression. A closure is created around the expression and
run asynchronously on process `p`. Returns a [`Future`](@ref) to the result.
Create a closure is created around the expression and run the closure
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this seems redundant

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

whoops


Create a closure around an expression and run the closure
asynchronously on process `p`. Returns a [`Future`](@ref) to the result.
Accepts two arguments, `p` and an expression.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps augmenting the signature (rather than describing the signature in the docstring body) would be more consistent with other docstrings?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I looked at a bunch of other macros in the docs and none of them list their args in the signature. I think that's worth doing but perhaps as a separate PR?

Copy link
Member

@Sacha0 Sacha0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm modulo the minor signature comment/question! :)

@kshyatt kshyatt merged commit b5a61db into master Jul 1, 2017
@kshyatt kshyatt deleted the ksh/parallelmovements branch July 1, 2017 00:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs This change adds or pertains to documentation parallelism Parallel or distributed computation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants