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 has joined #ste||ar
Yorlik_ has joined #ste||ar
Yorlik__ has quit [Ping timeout: 276 seconds]
diehlpk has quit [Quit: Leaving.]
hkaiser has quit [Quit: Bye!]
Kalium has quit [Ping timeout: 256 seconds]
Kalium has joined #ste||ar
Yorlik_ is now known as Yorlik
sestro[m] has quit [Quit: You have been kicked for being idle]
pansysk75[m] has quit [Quit: You have been kicked for being idle]
K-ballo has quit [Ping timeout: 244 seconds]
K-ballo has joined #ste||ar
hkaiser has joined #ste||ar
pansysk75[m] has joined #ste||ar
<hkaiser>
gonidelis[m]: yt?
diehlpk has joined #ste||ar
diehlpk has quit [Client Quit]
diehlpk_work has joined #ste||ar
<gonidelis[m]>
Not on my computer yet but here
<hkaiser>
gonidelis[m]: I had to move this week's Friday meeting to next Friday 9am CDT - just FYI as you wanted me to join your GSoC call...
<hkaiser>
satacker[m]: sorry, I didn't mean to rush (or even to scare) you
<satacker[m]>
Btw, workflow is now much nicer, faster builds, easy code changes sync
<satacker[m]>
thanks to gonidelis and rostam
<hkaiser>
cool
<gonidelis[m]>
Yay!
<satacker[m]>
hkaiser: No it's alright, I am just making sure I understand awaitables more clearly so that I can write tests which could test most of the scenarios
<hkaiser>
satacker[m]: ok
<hkaiser>
for q1: you might have to disable_if the first overload
<hkaiser>
q2: I don't think that an awaitable can be an awaiter at the same time
<hkaiser>
q3: awaitables have to expose three functions: await_ready, await_suspend, and await_resume
<satacker[m]>
hkaiser: Or I can enable if second one?
<hkaiser>
satacker[m]: you already enable_if'ed it, no?