hkaiser 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/ | GSoD: https://developers.google.com/season-of-docs/
diehlpk 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
hkaiser has quit [Ping timeout: 245 seconds]
jaafar has quit [Ping timeout: 258 seconds]
diehlpk has quit [Ping timeout: 245 seconds]
jaafar has joined #ste||ar
<K-ballo> simbergm: slightly.. pretty good, considering
hkaiser has joined #ste||ar
<heller> So, agent_ref or agent_proxy?
<hkaiser> heller: as you like it, it's not user-facing, so it's not that important
<heller> Depends on which type of user we're talking about
<hkaiser> 99of the users
<hkaiser> 99
<hkaiser> percent
<heller> The API is exposed to uses wanting to extend whatever we come up with
<heller> I guess
<hkaiser> sure
<hkaiser> agent_ref is fine
<hkaiser> I like the other better but can live with this
<heller> Why do you prefer proxy?
<hkaiser> difficult to anser
<hkaiser> function_ref is more of a 'permanent' reference to a function whereas the agent_ref is created locally and on a temporary basis - but this is a weak argument
<hkaiser> agent_ref is just fine, I guess
diehlpk has joined #ste||ar
jaafar has quit [Ping timeout: 276 seconds]
diehlpk has quit [Quit: Leaving.]
jaafar has joined #ste||ar
diehlpk has joined #ste||ar
diehlpk has quit [Ping timeout: 240 seconds]
jaafar has quit [Ping timeout: 240 seconds]
diehlpk has joined #ste||ar
USTOBRE has joined #ste||ar
diehlpk has quit [Quit: Leaving.]
<hkaiser> USTROBE: I think this whole paragraph is wrong nowadays
<hkaiser> on windows, just use vcpkg, on linux you have to ask somebody else ;-)
diehlpk has joined #ste||ar
diehlpk has quit [Client Quit]
diehlpk has joined #ste||ar
<zao> hkaiser: Feels a bit like a cop-out answer screwing over people who can't vcpkg for reasons. I definitely couldn't use it for any projects I've made. A text that uses those FindBoost defines should be largely platform-agnostic unless someone has screwed it up somewhere again.
diehlpk has quit [Client Quit]
<zao> Saying that everyone should just use vcpkg is like saying everyone should just use Conan :P
<zao> Do you say anything about what kind of build you need of Boost libraries by the way?
<zao> Dynamic linked, dynamic runtime?
<zao> Anyway, I'm not an user, take my thoughts with whatever fistfuls of salt you care about :)
<USTOBRE> @zao The section of the manual I'm looking at doesn't mention it. However, it could be located under a different section or use different wording. Do you think it's something that is important to mention?
nikunj has joined #ste||ar
<zao> Depends on what Hartmut's stance on Windows is. If the only supported method of using Boost is vcpkg, then Windows-specific instructions for using it via some other route aren't that releveant, unless you have actual needs to stray from the "supported" configuration.
<hkaiser> zao: lol - yah sure
nikunj has quit [Read error: Connection reset by peer]
jaafar has joined #ste||ar
hkaiser has quit [Read error: Connection reset by peer]