Making sure, that hpx::finalize can be called from any locality #1134
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
…hat only the first invocation triggers the termination.
|
Tests Failed. |
|
The remaining test failures are unrelated, this pull request is ready to be merged. |
sithhell
added a commit
that referenced
this pull request
May 15, 2014
Making sure, that hpx::finalize can be called from any locality
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.
Making sure, that
hpx::finalizecan be called from any locality and that only the first invocation triggers the termination.No API changes are caused, just fixes to the existing inconsistent behavior.