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-ballo has quit [Ping timeout: 256 seconds]
K-ballo has joined #ste||ar
diehlpk has joined #ste||ar
hkaiser has quit [Quit: Bye!]
diehlpk has quit [Quit: Leaving.]
Yorlik has joined #ste||ar
K-ballo has quit [Ping timeout: 256 seconds]
K-ballo has joined #ste||ar
hkaiser has joined #ste||ar
<srinivasyadav227> hkaiser: is ittnotify module used only when HPX_WITH_ITTNOTIFY is set to ON or is it built everytime ?
<hkaiser> srinivasyadav227: I think it's built always, but all headers have #ifdefs
<hkaiser> this is done to avoid having to sprinkle #ifdefs all over the codebase where ittnotify things are being used
<hkaiser> srinivasyadav227: in your case I think you can disable the module alltogether as there are close to none references to it in the rest of the codebase
<srinivasyadav227> how about doing this... appending to _hpx_core_modules here https://github.com/STEllAR-GROUP/hpx/blob/master/libs/core/CMakeLists.txt only if HPX_WITH_LIKWID is set ?
<hkaiser> srinivasyadav227: you can always add it there, just do something like: https://github.com/STEllAR-GROUP/hpx/blob/master/libs/core/async_mpi/CMakeLists.txt#L11-L13
<srinivasyadav227> cool, will do it that way, thanks!!
<srinivasyadav227> btw, #5858 is ready ;-)
<hkaiser> srinivasyadav227: ok, will have a look later today, thanks!
diehlpk_work has joined #ste||ar
diehlpk_work has quit [Ping timeout: 252 seconds]
K-ballo has quit [Ping timeout: 248 seconds]
K-ballo has joined #ste||ar
diehlpk_work 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
<satacker[m]> <hkaiser> "satacker: don't get fooled by..." <- ```
<satacker[m]> > <@hkaiser:libera.chat> satacker: don't get fooled by the meta stuff, this is really just the underlying machinery that computes the signatures, but you need to look at a concrete signatures type (provided as a template argument to receiver_of) and check whether R will accept all value_types that are listed in the... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/d2a4b4fc2a6bc6171dbe82c79a3cc0740ef19e0b)
<hkaiser> satacker[m]: almost
<satacker[m]> Not sure about the template arguments for value_types
<hkaiser> value_types is a variant of types variant<Ts...>, where for all of Ts... set_value should be a valid operation
<hkaiser> so is_invocable_v<set_value_t, decay_t<T>, Ts> should be true for all Ts...
<satacker[m]> So if Cs::sends_stopped is true it'll imply that there is infact a `set_stopped_t`
<hkaiser> satacker[m]: exactlt
<hkaiser> exactly
<hkaiser> satacker[m]: so it's three separate conditions, one for each set_value/error/stopped and all threemust be true
diehlpk_work has quit [Remote host closed the connection]
hkaiser has quit [Read error: Connection reset by peer]
hkaiser has joined #ste||ar