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
tufei__ has quit [Remote host closed the connection]
tufei_ has quit [Ping timeout: 276 seconds]
diehlpk has joined #ste||ar
K-ballo has quit [Quit: K-ballo]
diehlpk has quit [Quit: Leaving.]
hkaiser has quit [Quit: Bye!]
Yorlik has joined #ste||ar
Yorlik has quit [Read error: Connection reset by peer]
<ms[m]>
and you can essentially ignore the change in 5538 and keep your changes, since you've added that version requirement elsewhere in your pr
<dkaratza[m]>
so, how should i solve this? im not sure
<gnikunj[m]>
@hkaiser rori srinivasyadav227 : there's a slim chance that I do not make it to the meeting today. Please continue without me if that happens.
<dkaratza[m]>
ms: also changed the appearance of the headings in section "why hxp"
<dkaratza[m]>
but changing the headings from their level to a lower one didn t work. because the headings keep to appear just a level lower which is kind of weird in the navigation bar
<dkaratza[m]>
so i did it like that `.. raw:: html <h2>title</h2>` hope its not a problem
<jedi18[m]>
Regarding P2408R1, the problem outlined in the paper applies to HPX too since like MSVC we also check for iterator categories in our tag dispatch overloads right?
<hkaiser>
jedi18[m]: we static_assert, just checking for is_iterator
<hkaiser>
on the tag_dispatch
<hkaiser>
but it boils down to the same
<jedi18[m]>
Yeah I mean the static_asserts, it will fail to compile right
<hkaiser>
yes
<jedi18[m]>
Are we going to wait to see how LEWG reponds to that paper before doing anything about it?
<hkaiser>
can we do something about it?
<jedi18[m]>
proposal*
<hkaiser>
I need to read it again
<jedi18[m]>
Ok
<K-ballo>
we should try it out, let LEWG know how it went
<jedi18[m]>
Well we don't require c++ 20 and since we don't have iterator concepts in HPX we can't use the solution they propose
<K-ballo>
none of that is a show stopper
<ms[m]>
dkaratza: have you ever done a rebase? if not, look into it or let me know if you'd like to have a look together
<ms[m]>
that'll let you handle the conflict
<ms[m]>
also, I doubt that we need to put raw html in the docs (it won't work for the pdf either...)
<jedi18[m]>
K-ballo: So you mean we could add the iterator concepts?
<ms[m]>
I'm not quite sure I understand the problem you're having with the headings... we can perhaps also have a short call and you can show me
<K-ballo>
I don't know what you have in mind for "add the iterator concepts", but in some form or other, yeah
<K-ballo>
the important part is implementing the algorithms in terms of them, which should only require minor adjustments (or if it doesn't, that's important for LEWG to know)
<hkaiser>
our is_foo_iterator essentially check for the type concepts
<jedi18[m]>
Ohh ok, well then it should be fairly easy to do
<jedi18[m]>
Shall I?
<hkaiser>
please feel free to play around, sure
<jedi18[m]>
Ok thanks
<hkaiser>
jedi18[m]: did you have a chance to separate the _t/_v changes from the partition PR?
<jedi18[m]>
Yep, the PR is ready
<hkaiser>
ohh, cool!
<hkaiser>
gnikunj[m]: yt?
<gonidelis[m]>
hkaiser: just saw that. wow! they are ahead of us now
diehlpk has joined #ste||ar
<gnikunj[m]>
hkaiser here now
diehlpk has quit [Quit: Leaving.]
diehlpk has joined #ste||ar
<hkaiser>
gnikunj[m]: hey
<hkaiser>
gonidelis[m]: yep, let's get going, then
<gnikunj[m]>
hkaiser see pm pls
tufei_ has joined #ste||ar
<dkaratza[m]>
<ms[m]> "also, I doubt that we need to..." <- so, how should i do it? i cant find any other way
tufei__ has joined #ste||ar
tufei_ has quit [Remote host closed the connection]