aserio changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar.cct.lsu.edu | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | Buildbot: http://rostam.cct.lsu.edu/ | Log: http://irclog.cct.lsu.edu/
<hkaiser>
taeguk[m]: yt?
EverYoung has quit [Ping timeout: 246 seconds]
<github>
[hpx] taeguk opened pull request #2819: Fix compile errors in unit test of container version of parallel::partition. (master...tg_partition_fix2) https://git.io/v79o2
<github>
[hpx] taeguk opened pull request #2820: Support C++11 in benchmark codes of parallel::partition and parallel::partition_copy. (master...tg_partition_benchmark_cmake) https://git.io/v7960
hkaiser has quit [Quit: bye]
K-ballo has quit [Quit: K-ballo]
vamatya has joined #ste||ar
<github>
[hpx] taeguk opened pull request #2821: Fix a bug which related to HPX_HAVE_CXX11_AUTO_RETURN_VALUE in CMakeLists.txt. (master...tg_cmake_auto_return_value) https://git.io/v791k
<github>
[hpx] hkaiser created fixing_2822 (+1 new commit): https://git.io/v7H8B
<github>
hpx/fixing_2822 b36b199 Hartmut Kaiser: Making sure promises are marked as started when used as continuations
<github>
[hpx] hkaiser opened pull request #2824: Making sure promises are marked as started when used as continuations (master...fixing_2822) https://git.io/v7H80
bikineev has joined #ste||ar
pree_ has joined #ste||ar
pree has quit [Ping timeout: 248 seconds]
pree_ is now known as pree
<github>
[hpx] hkaiser force-pushed fixing_2822 from b36b199 to b9e53d3: https://git.io/v7H4g
<github>
hpx/fixing_2822 b9e53d3 Hartmut Kaiser: Making sure promises are marked as started when used as continuations
pree has quit [Quit: AaBbCc]
denis_blank has joined #ste||ar
bikineev has quit [Remote host closed the connection]
bikineev has joined #ste||ar
vamatya has quit [Ping timeout: 258 seconds]
Matombo has quit [Remote host closed the connection]
taeguk[m] has quit [Ping timeout: 246 seconds]
thundergroudon[m has quit [Ping timeout: 246 seconds]
<github>
[hpx] hkaiser pushed 1 new commit to partitioned_vector: https://git.io/v7HEd
<github>
hpx/partitioned_vector 3eaff5c Hartmut Kaiser: Merge branch 'master' into partitioned_vector
<K-ballo>
denis_blank: could you give the pack-short-circuit branch a try and see if you can reproduce circle's error for tests.unit.lcos.local_dataflow_executor_v1?
<K-ballo>
denis_blank: disregard that, it's the wrong dataflow
<denis_blank>
K-ballo: All right, it's really confusing that both dataflow files are named the same
<hkaiser_>
denis_blank: yah, and the local one #includes the remote one which is counter-intuitive as well ...
<denis_blank>
Once I was wondering why dataflow can't be used on simple arguments and required a policy... it was because I included the wrong file^^
<hkaiser_>
heh
<hkaiser_>
always use hpx/include/dataflow.hpp ;)
<hkaiser_>
at least for things outside of hpx
<K-ballo>
I'm not sure what it's going on with that test
<K-ballo>
something that was callable stops being callable, I guess
<hkaiser_>
I think dataflow should not 'explode' the arguments at all
<denis_blank>
hkaiser_: Do you mean it shouldn't change the arguments or that it should only wait for the futures in the first depth: dataflow(..., future<int>, tuple<future<float>>) -> wait on future<float> or not?
<hkaiser_>
shouldn't change arguments
<hkaiser_>
but yah, it would be nice if it was waiting for futures on all levels recusively
<denis_blank>
Changing of the arguments wasn't intended, because I thought dataflow was designed to pass the arguments through right? I planned to wait on the futures on all levels.