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
Yorlik_ has joined #ste||ar
Yorlik has quit [Ping timeout: 248 seconds]
ahmed_ has quit [Quit: Connection closed for inactivity]
Guest7 has joined #ste||ar
K-ballo has quit [Quit: K-ballo]
Guest71 has joined #ste||ar
Guest7 has quit [Quit: Client closed]
hkaiser has quit [Quit: Bye!]
Guest7 has joined #ste||ar
Guest71 has quit [Quit: Client closed]
Guest7 has quit [Ping timeout: 250 seconds]
ruchipakhle has joined #ste||ar
ruchipakhle has quit [Quit: Client closed]
ruchipakhle has joined #ste||ar
ruchipakhle has quit [Quit: Client closed]
ruchipakhle has joined #ste||ar
ruchi_ has joined #ste||ar
ruchi_ has quit [Client Quit]
pansysk75[m] has joined #ste||ar
ruchipakhle has quit [Quit: Client closed]
hkaiser has joined #ste||ar
K-ballo has joined #ste||ar
<pansysk75[m]>
Greetings! I'm interested in joining the GSoC project. Do you suggest Windows + Visual Studio + vcpkg for getting started building and exploring HPX?
ahmed_ has joined #ste||ar
<hkaiser>
pansysk75[m]: yes, that's a good choice
<hkaiser>
pansysk75[m]: you might want to build hpx outside of vcpkg if you want to change it, if you're interested in wrting code using hpx then installing it with vcpkg is a good start
<hkaiser>
I think the basic co_await support for senders/receivers should not rely on hpx::future
<satacker[m]>
So there should be a base promise type ?
<satacker[m]>
* > I think the basic co_await support for senders/receivers should not rely on hpx::future
<satacker[m]>
So there should be a base promise type ?
<hkaiser>
one of the points of S/R is to avoid the allocations asociated with futures, also, futures are single use, whereas S/R in general can be used (started) multiple times
<hkaiser>
most likely there has to be a promise type (as in the example code I linked above)
<satacker[m]>
hkaiser: And also a base type for awaitable
<satacker[m]>
What would be the major difference between the implementations of non-hpx libraries? custom allocator for promise type?
<hkaiser>
satacker[m]: there might not be too many differences, actually
<satacker[m]>
I haven't used any library building c++ as I haven't written one. But assuming I understand this project now and with the c++ lectures you have put up coupled with boost programming guide I might actually be able to do this project.
<hkaiser>
satacker[m]: sure, also we're here to help
<satacker[m]>
Thanks for all the help until now, although I'll need to ping you on email once I complete draft of the proposal
<hkaiser>
satacker[m]: please do
ahmed_ has quit [Quit: Connection closed for inactivity]
ahmed_ has joined #ste||ar
ahmed_ has quit [Quit: Connection closed for inactivity]
<gonidelis[m]>
dimpapag: is there possible that you publish your proposal using google docs to facilitate the feedback procedure?
diehlpk has joined #ste||ar
<gonidelis[m]>
oh does it not let you at all? weird...kinda loses its whole "google ecosystem" purpose