We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
hpx/hpx/parallel/algorithms/sort.hpp
Lines 210 to 214 in f63f4b9
result(hpx::future) is returned from execution::async_execute(). So, if the task is running, result.has_exception() always returns false.
result
execution::async_execute()
result.has_exception()
false
As I think, that code block(L210-L214) is not necessary because anyhow the exception which is occurred in the task is wrapped into the future(result).
The text was updated successfully, but these errors were encountered:
Fix a strange thing in parallel::detail::handle_exception.
ce021a1
There are some changes in parallel::sort for fixing STEllAR-GROUP#2834. And this commit also fixes STEllAR-GROUP#3088.
No branches or pull requests
hpx/hpx/parallel/algorithms/sort.hpp
Lines 210 to 214 in f63f4b9
result
(hpx::future) is returned fromexecution::async_execute()
. So, if the task is running,result.has_exception()
always returnsfalse
.As I think, that code block(L210-L214) is not necessary because anyhow the exception which is occurred in the task is wrapped into the future(
result
).The text was updated successfully, but these errors were encountered: