bita_ has quit [Read error: Connection reset by peer]
bita_ has joined #ste||ar
hkaiser has quit [Quit: bye]
Nikunj__ has joined #ste||ar
nikunj97 has quit [Ping timeout: 256 seconds]
nikunj97 has joined #ste||ar
Nikunj__ has quit [Ping timeout: 265 seconds]
Nikunj__ has joined #ste||ar
nikunj97 has quit [Ping timeout: 256 seconds]
Nikunj__ has quit [Quit: Leaving]
Yorlik has joined #ste||ar
bita_ has quit [Ping timeout: 260 seconds]
Yorlik has quit [Ping timeout: 264 seconds]
K-ballo has quit [*.net *.split]
K-ballo has joined #ste||ar
Yorlik has joined #ste||ar
nikunj97 has joined #ste||ar
<nikunj97>
K-ballo, if I have to suggest books to C++ novice to learn modern C++ and advanced C++ features (template metaprogramming, SFINAE etc.), which one's should I suggest? Also in what order?
hkaiser has joined #ste||ar
<K-ballo>
nikunj97: I wouldn't know
<nikunj97>
K-ballo, yea. That's what I said as well. Wanted to know if there's actually a guide or so for it.
<K-ballo>
there's a popular SO question on c++ books
<zao>
Not sure about the quality of them, but the C++ Weekly videos on particular parts of the language are probably decent introductions to a lot of things.
<nikunj97>
ohh so apply and async functions for them
<nikunj97>
I get it
<hkaiser>
nikunj97: the difference is the id_type, it's 'delivered' by the policy
<nikunj97>
as in?
hkaiser_ has joined #ste||ar
<hkaiser_>
nikunj97: I was never happy with the way things were implemented
<nikunj97>
you mean binpacking or all distributed policies?
<hkaiser_>
the whole execution could be separated from the distribution policy as all itwould need would be to call get_next_target() on it, the rest should be the same for all
<hkaiser_>
would have to be rewritten to just call get_next_target on the policy and dispatch to the base async() implementation
<nikunj97>
aha, so it couldn't find the async function when called from here
<hkaiser_>
yes
hkaiser has quit [Ping timeout: 240 seconds]
<hkaiser_>
then we could remove the execution part from all distribution policies
<nikunj97>
this does not sound like a great implementation
<hkaiser_>
let me do that, shouldn't take too long
<nikunj97>
I think, this execution policies should just be wrappers to how it will be executing and not include the invocation themselves. That should be a template specialization within async
<nikunj97>
I think I read something similar in Andrei's book
<hkaiser_>
I think what needs to be done, the distributon policies shouldn't have any code, all they need is the get_next_target function
<hkaiser_>
not sure why I have not seen this before :/
<nikunj97>
well technically yes. But having invocation within all distribution policies sound a bit redundant. The policies themselves assign the localities on which they'll be invoked. One can use a single invocation and the policy to make it work, no?
bita_ has joined #ste||ar
<hkaiser_>
nikunj97: that's what I meant
<hkaiser_>
also, I think it makes sense for the binbacking policy not to do execution
<nikunj97>
ohh I must've misinterpreted then
<nikunj97>
hkaiser_, yes agreed
<hkaiser_>
this one is all about allocation anyways, but I guess for some work-load balancing it might be useful
<hkaiser_>
nikunj97: I'll work on some changes for the policies
<nikunj97>
I need to do a call with parsa. I need load balancing capabilities to have a working distributed resiliency model
<nikunj97>
hkaiser_, thanks a lot
akheir has joined #ste||ar
Nikunj__ has joined #ste||ar
nikunj97 has quit [Ping timeout: 240 seconds]
<nanmiao11>
I got an error "/home/nanmiao/Documents/project/dev/src/phylanx/src/execution_tree/primitives/assert_condition.cpp:10:10: fatal error: hpx/distributed/iostream.hpp: No such file or directory #include <hpx/distributed/iostream.hpp>". Any one has the same issue?