K-ballo 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/
bita has joined #ste||ar
bita has quit [Ping timeout: 258 seconds]
hkaiser has quit [Quit: bye]
paraz[m] has joined #ste||ar
paraz[m] has left #ste||ar [#ste||ar]
shahrzad_ has quit [Quit: Leaving]
jehelset has joined #ste||ar
henrietaMag has joined #ste||ar
henrietaMag has quit [K-Lined]
hkaiser has joined #ste||ar
jehelset has quit [Remote host closed the connection]
<hkaiser>
gnikunj[m]: yt?
<gnikunj[m]>
hkaiser here
<hkaiser>
see m, pls
<hkaiser>
pm
hkaiser has quit [Read error: Connection reset by peer]
<hkaiser>
gnikunj[m]: the BaseExecutor is just referenced (i.e. the user has to keep it alive)
<hkaiser>
gnikunj[m]: alternatively, you could forward the executor, but then it would be difficult to use it vanilla for anything except inside the replay_executor
<gnikunj[m]>
I didn't get what you mean
<hkaiser>
I guess storing the executor as a forwarding reference might work, f it's used with an lvalue, it will be just referenced, if initialized from an rvalue, then it's embedded
<gnikunj[m]>
yeah, that's what I was thinking
<gnikunj[m]>
if it's an rvalue, it isn't really supposed to have a lifetime outside of our executor
<hkaiser>
feel free to change it
<gnikunj[m]>
if it's an lvalue, we're storing it as reference (that's what we're doing now already)
<gnikunj[m]>
<hkaiser "feel free to change it"> just wanted to make sure if my thinking was right. I'll use perfect forwarding then :D
<hkaiser>
k
<gnikunj[m]>
hkaiser: why do you decay Validate type while forwarding Validate as is?