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
Add hpx::start nullptr overloads #3127
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please add equivalent overloads to hpx::init()
?
hpx::start
nullptr overloads
Added overloads to |
@@ -705,6 +707,18 @@ namespace hpx | |||
inline int init(util::function_nonser<int(int, char**)> const& f, | |||
int argc, char** argv, std::vector<std::string> const& cfg, | |||
hpx::runtime_mode mode = hpx::runtime_mode_default); | |||
|
|||
/// \cond NOINTERNAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's your rationale not to document the new overloads? Do you intend to deliberately leave them 'undocumented' (in the sense that the user is not supposed to use them)?
I did not mean for users not to use them. My thinking was that the
nullptr overloads are just an implementation detail to get the correct
behaviour for existing overloads, but in that case I should probably
document the behaviour in the affected overloads.
As a user, would you prefer to see the nullptr overloads explicitly
documented with separate entries or to have the nullptr behaviour
documented in the existing entries?
|
Having it documented as a special case with the other overloads would be preferred, I think. Something like: if |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks a lot!
I also added a further note about |
ef22f2f
to
488174c
Compare
Proposed Changes
Adds overloads so that passing
nullptr
tohpx::start
will only start up the runtime.This also adds a missing line to the docstrings of some
hpx::start
overloads.