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/
K-ballo has quit [Quit: K-ballo]
hkaiser has quit [Quit: bye]
sivoais has quit [Ping timeout: 246 seconds]
sivoais has joined #ste||ar
rainmaker[m] is now known as rainmaker6[m]
syrex has joined #ste||ar
bita has quit [Ping timeout: 250 seconds]
jaafar has quit [Ping timeout: 245 seconds]
jaafar has joined #ste||ar
parsa has quit [Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net]
parsa has joined #ste||ar
K-ballo has joined #ste||ar
jehelset has quit [Remote host closed the connection]
<gonidelis[m]> K-ballo: can a sentinel be both a value and distance?
<gonidelis[m]> sorry
<gonidelis[m]> can a sentinel be either a value or a distance? ^^
<K-ballo> a sentinel can't not be a value, what else would it be?
<gonidelis[m]> K-ballo: isn't this a sentinel value?
<gonidelis[m]> {50}
<K-ballo> "sentinel value" isn't a thing, `50` is a value, `sentinel<std::int16_t>{50}` is also a value and one of sentinel type (a type that models sentinel)
hkaiser has joined #ste||ar
<gonidelis[m]> K-ballo: ok great
<gonidelis[m]> now if i wanted to make a sentinel type that accepts both distances and values
<gonidelis[m]> how would i make it distinguish them
<gonidelis[m]> say `sentinel<std::int16_t>{50}`
<gonidelis[m]> how does it know if 50 is +50 or "find the value 50" ?
<K-ballo> however you wish
<gonidelis[m]> what are the options
<gonidelis[m]> from user's prespective they just give me a "50"
<gonidelis[m]> how do they tell me if it's a distance or a value
<gonidelis[m]> ?
<K-ballo> named constructors, tags
<gonidelis[m]> so they need to specify it
<gonidelis[m]> it's a little vague
<gonidelis[m]> idk
<K-ballo> there's nothing sentinel-y specific about it, it's just your typical class design
<K-ballo> and sounds like a pretty poor class design, since it has two different purposes
<gonidelis[m]> is it a good idea for c++23 to provide out of the box sentinel types?
<K-ballo> unlikely
<gonidelis[m]> hm ok
<gonidelis[m]> soudns good to me
hkaiser has quit [Read error: Connection reset by peer]
hkaiser has joined #ste||ar
<hkaiser> gnikunj[m]: will you join?
<gnikunj[m]> hkaiser joining in 2min
nanmiao has joined #ste||ar
bita has joined #ste||ar
bita has quit [Ping timeout: 245 seconds]
nanmiao has quit [Quit: Connection closed]
nanmiao has joined #ste||ar
nanmiao has left #ste||ar [#ste||ar]
nanmiao has joined #ste||ar
nanmiao has quit [Quit: Connection closed]
HaimantikaMitra[ has quit [Ping timeout: 276 seconds]
HaimantikaMitra4 has joined #ste||ar
gnikunj[m] has quit [Ping timeout: 276 seconds]
old_man[m] has quit [Ping timeout: 276 seconds]
dashohoxha[m] has quit [Ping timeout: 276 seconds]
gonidelis[m] has quit [Ping timeout: 276 seconds]
rori has quit [Ping timeout: 276 seconds]
old_man[m] has joined #ste||ar
gnikunj[m] has joined #ste||ar
dashohoxha[m] has joined #ste||ar
rori has joined #ste||ar
gonidelis[m] has joined #ste||ar
<parsa> hkaiser: ping
<hkaiser> parsa: here
<parsa> is HPX being tested anywhere with Vc support enabled?
<hkaiser> yes, on circleci
<parsa> looking at https://app.circleci.com/pipelines/github/STEllAR-GROUP/octotiger/575/workflows/c15f5b03-2b7c-424e-84fa-7951c56ebacf/jobs/8248 it looks like just doing include <hpx/parallel/traits/vector_pack_type.hpp> breaks the build
<hkaiser> parsa: isn't that unrelated?
<hkaiser> I think it misses <hpx/modules/collectives.hpp>
<parsa> i used to think that stuff is Vc-related
<hkaiser> parsa: I wouldn't think so
<parsa> even better
<gnikunj[m]> hkaiser: finally done with the slides \o/
<hkaiser> gnikunj[m]: \o/
<gnikunj[m]> I've sent it to Keita for approval. I don't think I want to make any changes to them now xD
<parsa> hkaiser: that wasn't it
<parsa> same error now from collectives.hpp
<parsa> pretty sure it's not even reaching the broadcast there. see: https://pastebin.com/2vTfZ5Mr
<hkaiser> parsa: that's a different error
<gnikunj[m]> K-ballo: woah! Are you going to face copyrights now?
<gnikunj[m]> lol my bad. Seems like Google gives out this image as the logo for HPX when you search for it: https://www.google.com/search?q=hpx&oq=hpx+&aqs=chrome.0.69i59l2j35i39j69i60l4j69i65.1023j0j4&sourceid=chrome&ie=UTF-8
<parsa> hkaiser: i can't tell them apart... what is the difference?
<hkaiser> not related to broadcast anymore
<hkaiser> looks like more headers are missing
<parsa> hkaiser: i do see a few errors complaining about HPX_REGISTER_BROADCAST_ACTION_DECLARATION in the previous log not present in the new one, but the most of errors in both complain about `datapar_policy` stuff
<hkaiser> parsa: look at the first error and fix it, rerinse