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
<gonidelis[m]>
hkaiser: see pm please
hkaiser has quit [Quit: Bye!]
Yorlik_ has joined #ste||ar
Yorlik has quit [Ping timeout: 260 seconds]
Yorlik_ has quit [Read error: Connection reset by peer]
Yorlik has joined #ste||ar
Undername has joined #ste||ar
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 240 seconds]
K-ballo1 is now known as K-ballo
Undername has quit [Client Quit]
Undername has joined #ste||ar
hkaiser has joined #ste||ar
<dkaratza[m]>
hkaiser: when I get a warning about an argument not found, should I remove the argument from the documentation or add it in the code? I guess the answer is to remove it from the doxygen docs, right?
<satacker[m]>
Within the namespace `hpx::execution::experimental::detail` that happens to be used for implementations cannot we reuse the code within another header and same namespace ?
<satacker[m]>
For example the `is_completion_signature` is already implemented in detail:: completion_signatures.hpp , however it is not visible within detail:: of receiver.hpp