Hartmut Kaiser
Hartmut Kaiser
Alternatively we could make the current implementation of `get_id` call the `get_outer_self_id` instead. Not sure what this would break, though...
We can make this attribute conditional, though.
We do have `HPX_UNUSED`, however its use is different from `[[maybe_unused]]`. So instead of writing: ``` void foo([[maybe_unused]] int bar) {} ``` one would have to write: ``` void foo(int...
> So everywhere we use [[maybe_unused]] should be replaced with HPX_UNUSED No! Everywhere possible where we currently use `HPX_UNUSED` we should use `[[maybe_unused]]` instead. > or we could have another...
@beojan I'm not able to reproduce this issue locally. What application did you run?
@beojan would you have more information on how we could reproduce this issue? Are you using any specific environment?
@Johan511 thanks for adding the tests. The last thing missing here is to add the documentation for the algorithms. All other algorithms have extensive documentation. Please coordinate with @dimitraka on...
You used `-DCMAKE_CXX_FLAGS=-stdlib=libc++` while configuring HPX, I'd expect you need to do the same for all depending projects.
@Johan511 could you create graphs that use the same y-axis limits, please?
The code you proposed touches on sequential operations only. Could you measure the sequential speedup as well?