hkaiser changed the topic of #ste||ar to: The topic is '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/
primef has joined #ste||ar
primef has quit [Remote host closed the connection]
d067751 has joined #ste||ar
d067751 has left #ste||ar [#ste||ar]
primef has joined #ste||ar
primef has quit [Ping timeout: 246 seconds]
hkaiser has quit [Quit: bye]
parsa has quit [Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net]
parsa has joined #ste||ar
primef has joined #ste||ar
Yorlik has joined #ste||ar
<Yorlik> Do we have a list somewhere what needs to be included for which construct to use?
<Yorlik> A synopsis of some sort?
<K-ballo> no, not really, but I believe end users are supposed to use the coarse hpx/include/ headers
<K-ballo> and there should be some kind of namespace to header correspondance, ideally?
<Yorlik> Alright. Thanks.
<Yorlik> logic is always appreciated :)
hkaiser has joined #ste||ar
hkaiser has quit [Ping timeout: 245 seconds]
hkaiser has joined #ste||ar
primef has quit [Ping timeout: 268 seconds]
primef has joined #ste||ar
primef has quit [Ping timeout: 272 seconds]
primef has joined #ste||ar
primef has quit [Ping timeout: 246 seconds]
primef has joined #ste||ar