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
K-ballo has quit [Quit: K-ballo]
<gonidelis[m]>
hkaiser: yt?
hkaiser has quit [Quit: Bye!]
ruchipakhle has joined #ste||ar
Yorlik has joined #ste||ar
ruchipakhle has quit [Quit: Client closed]
ruchipakhle has joined #ste||ar
ruchipakhle has quit [Client Quit]
ruchipakhle has joined #ste||ar
ruchipakhle has quit [Quit: Client closed]
ruchipakhle has joined #ste||ar
hkaiser has joined #ste||ar
K-ballo has joined #ste||ar
ruchipakhle has quit [Quit: Client closed]
hkaiser has quit [Read error: Connection reset by peer]
diehlpk_work has joined #ste||ar
hkaiser has joined #ste||ar
<srinivasyadav227>
hkaiser: does `decorated_iterator` in unit tests disable any functionalities of `base_iterator` that is passed ?
<hkaiser>
we should probably make sure nobody #includes it directly
<hkaiser>
I don't think this causes your 'weirdness', though
<hkaiser>
from what I can tell, the serialization code looks ok to me (well the first serialize function)
<hkaiser>
the second one can't compile as getX/getY don't return references
<hkaiser>
serialize is called on both ends of the wire, for serilization and deserialization (with two different Archives)
<hkaiser>
one of those (the deserialization) will fail with the second serialize function
<john98zakaria[m]>
Is it possible to serialize a class that you don't control ?
diehlpk_work has quit [Remote host closed the connection]
<hkaiser>
only if you have access to the members in some way
<john98zakaria[m]>
getters wouldn't suffice ?
<hkaiser>
you can serialize things non-intrusively (by adding a global function)
<hkaiser>
getters will be sufficient for the serialization part, but not the de-serialization as that needs to create a new instance of the object on the receiving end
<hkaiser>
so you need to have a) access to the members, or b) be able to fully initialize the object using one of its constructors
<hkaiser>
john98zakaria[m]: it also depends on whether your type has a default constructor or not
<john98zakaria[m]>
How would I serialize my Point class assuming i can't access the members directly
<hkaiser>
does it have a default constructor?
<john98zakaria[m]>
PointClass() =default;
<hkaiser>
yes it has, good - that simplifies things
<john98zakaria[m]>
hkaiser: /home/jn98zk/CLionProjects/HelloHPX/SendCustomType.cpp:86:1: error: no matching function for call to ‘load(hpx::serialization::input_archive&, PointClass&, int)’
<hkaiser>
john98zakaria[m]: move the macro after the load/save definitions