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/
RostamLog has joined #ste||ar
rod_t has left #ste||ar [#ste||ar]
<K-ballo>
we have more than twice as much bind_fronts than bind_backs.. I was expecting more bind_backs
<K-ballo>
although I did use bind_front when there were no placeholders at all, so who knows
<hkaiser>
you should use bind_back in those cases to increase the number of use cases ;)
<K-ballo>
indeed
aserio has quit [Quit: aserio]
<K-ballo>
...I might actually do that
<hkaiser>
K-ballo: frankly I was wondering why you chose to use bind_front, I somehow did expect to use bind_back for those cases, don't kno wwhy
<K-ballo>
yeah, ok, I'll actually do that, hold the PR a bit longer
<hkaiser>
sure
<hkaiser>
K-ballo: where in the code does the unwrapping for future::then happen?
<hkaiser>
can't find it
<hkaiser>
well, I found the type calculations, but not the actual unwrapping
<K-ballo>
uhm, in local/packaged_continuations somewhere.. let me see