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
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 268 seconds]
K-ballo1 is now known as K-ballo
K-ballo has quit [Quit: K-ballo]
K-ballo has joined #ste||ar
Yorlik has joined #ste||ar
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 268 seconds]
K-ballo1 is now known as K-ballo
<dkaratza[m]>
hkaiser: when I have a return type `replace_copy_result<typename hpx::traits::range_iterator<Rng>::type,
<dkaratza[m]>
OutIter>` for example for `replace_copy()`
<dkaratza[m]>
should `::type` be included in the docs? I thought it should be identical with the code but if I include it, I am getting warnings..
<K-ballo>
what kind of warnings?
<dkaratza[m]>
<K-ballo> "what kind of warnings?" <- when building the docs
<dkaratza[m]>
I am getting `warning: explicit link request to 'type' could not be resolved`