hkaiser changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar-group.org | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | This channel is logged: irclog.cct.lsu.edu
diehlpk_work has quit [Ping timeout: 258 seconds]
Yorlik_ has joined #ste||ar
Yorlik has quit [Ping timeout: 248 seconds]
K-ballo has quit [Ping timeout: 256 seconds]
K-ballo has joined #ste||ar
hkaiser has quit [Quit: Bye!]
<satacker[m]>
<hkaiser> "does it miss the #include?" <- No I did not. It's silly, I know we can do it. It's just a build system problem I guess. It says cannot find it within that namespace.
<satacker[m]>
* find it declared within that
K-ballo has quit [Ping timeout: 256 seconds]
ericniebler[m] has quit [Quit: You have been kicked for being idle]
K-ballo has joined #ste||ar
hkaiser has joined #ste||ar
hkaiser has quit [Quit: Bye!]
hkaiser has joined #ste||ar
hkaiser has quit [Ping timeout: 272 seconds]
hkaiser has joined #ste||ar
<srinivasyadav227>
hkaiser: yt?
K-ballo has quit [Remote host closed the connection]
K-ballo has joined #ste||ar
calla has joined #ste||ar
calla has quit [Quit: Leaving]
hkaiser has quit [Ping timeout: 252 seconds]
hkaiser has joined #ste||ar
<hkaiser>
srinivasyadav227: here now
<gonidelis[m]>
K-ballo: in what case would you want your constructor to be explicit? in other words, what's the motivation behind `explicit` ?
<hkaiser>
avoid accidental conversion from an unrelated type
<hkaiser>
struct A { A(int) {} }; is default constructible from an int, i.e. void foo(A) {} will accept and int: foo(42);
<hkaiser>
while struct A { explicit A(int) {} ); would not allow for this to happen
<hkaiser>
you'd have to write foo(A(42)); instead
<gonidelis[m]>
hkaiser_: too :)
hkaiser has quit [Quit: Bye!]
<gonidelis[m]>
he delivered. he quitted
hkaiser has joined #ste||ar
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 256 seconds]
K-ballo1 is now known as K-ballo
diehlpk has joined #ste||ar
diehlpk1 has joined #ste||ar
diehlpk has quit [Ping timeout: 255 seconds]
Yorlik_ is now known as Yorlik
<Yorlik>
hkaiser: YT?
diehlpk1 has quit [Quit: Leaving.]
diehlpk has joined #ste||ar
<satacker[m]>
hkaiser: gonidelis How do I unpack the completion signatures that are generated using `meta::pack<Signatures...>` ?
<hkaiser>
satacker[m]: you look at each of the signature types separately, i.e. cs::value_types, cs::error_types, and cs::sends_stopped
<Yorlik>
hkaiser: How would I send an output archive over he network? We use blobs (start, size) to pack data and send it over reliable, connection-aware UDP (when too big as fragments). Do we have examples for this?
<hkaiser>
satacker[m]: don't get fooled by the meta stuff, this is really just the underlying machinery that computes the signatures, but you need to look at a concrete signatures type (provided as a template argument to receiver_of) and check whether R will accept all value_types that are listed in the cs::value_types signature for set_value, etc.
<hkaiser>
Yorlik: you don't
<hkaiser>
you send the buffer that was used to construct the output archive
<Yorlik>
IC. So I reconstruct an input archive from that buffer on the receiving end.