aserio 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/
<K-ballo>
great, my little reproducer of the instantiation order issue isn't reproducing the issue anymore
<hkaiser>
K-ballo: have not seen this yet, thanks
<zao>
Gaaah. Waist-deep in databases instead of writing the code I wanted to.
<zao>
Upside of things, thinking about the schema up-front helps :)
<K-ballo>
hkaiser: what are distribution policies? and are they coming back?
<K-ballo>
I think I found the trouble makers.. I need to untangle dataflow and local::dataflow, right not they are intertwined in their dispatching
<hkaiser>
K-ballo: distribution policies are a failed attempt at something like executors but for distributed execution
<hkaiser>
they ended up being a 'all except the kitchen sink', clearly need another attempt
<hkaiser>
K-ballo: I think async and local async are entagled in a very similar way as dataflow
<K-ballo>
somewhat, yeah
<K-ballo>
I'm going to try to split dataflow so that local dataflow disappears when given an action, and add another overload to non-local dataflow to handle the action case
<K-ballo>
so that the dispatch trait specializations don't get split across files
<K-ballo>
remote and local each on its own file
<K-ballo>
that's going to make it easier to trace and diagnose the instantiation error
<hkaiser>
K-ballo: ok, makes sense
<hkaiser>
K-ballo: I seem to remember though, that one of the traits was needed for both, thus it's split over two iles
<K-ballo>
with one overload each, it is yeah
hkaiser has quit [Quit: bye]
wash has joined #ste||ar
K-ballo has quit [Quit: K-ballo]
EverYoung has quit [Remote host closed the connection]
wash has quit [Quit: Lost terminal]
wash has joined #ste||ar
EverYoung has joined #ste||ar
EverYoung has quit [Ping timeout: 258 seconds]
jbjnr has quit [Quit: ChatZilla 0.9.93 [Firefox 56.0.1/20171002220106]]
jbjnr has joined #ste||ar
pree has joined #ste||ar
pree has quit [Read error: Connection reset by peer]
pree has joined #ste||ar
pree has quit [Read error: Connection reset by peer]
pree has joined #ste||ar
wash has quit [Quit: leaving]
wash has joined #ste||ar
wash has quit [Quit: leaving]
hkaiser has joined #ste||ar
K-ballo has joined #ste||ar
pree has quit [Ping timeout: 248 seconds]
jaafar has joined #ste||ar
jaafar has quit [Ping timeout: 255 seconds]
eschnett has quit [Ping timeout: 240 seconds]
eschnett has joined #ste||ar
eschnett has quit [Quit: eschnett]
eschnett has joined #ste||ar
eschnett has quit [Read error: Connection reset by peer]
eschnett has joined #ste||ar
gedaj has joined #ste||ar
gedaj has quit [Quit: Leaving]
gedaj has joined #ste||ar
<jbjnr>
I get a lot of lockups with the latest master on shutdown
<github>
[hpx] biddisco created namespace_error (+1 new commit): https://git.io/vdME1
<github>
hpx/namespace_error 01148c4 John Biddiscombe: Fix a namespace compilation error when some schedulers are disabled