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/
hkaiser has joined #ste||ar
bita_ has quit [Ping timeout: 260 seconds]
hkaiser has quit [Quit: bye]
akheir has quit [Quit: Leaving]
<ms[m]>
K-ballo, yeah no rule to use `hpx/modules/*`, mostly convenience, so go for more specific includes where you know what you need exactly
<K-ballo>
so it was just laziness then, that's good to know, it can be fixed
<K-ballo>
there's still ground for a fundamentals module, for dependency reasons, those fundamental utilities are bundling with complex high level stuff in their modules
parsa has joined #ste||ar
parsa has quit [Client Quit]
parsa has joined #ste||ar
<ms[m]>
K-ballo: yep, if you think that's worth it that should be doable ("only" some rearranging of files)
<ms[m]>
and we've been trying to keep the public headers divorced from the modules, so `hpx/functional.hpp` doesn't need to come from the functional module for example