00:07 <K-ballo> gnikunj[m]: don't do that..

00:07 <K-ballo> mutable "copy" constructors make no sense

00:07 <gnikunj[m]> why's that?

00:07 <K-ballo> the semantic requirements of a copy constructor is that it doesn't mutate the source

00:08 <gnikunj[m]> aah, so it MUST be a const

00:08 <K-ballo> what are you actually trying to do?

00:08 <gnikunj[m]> Umm, I wanted to copy in a way that actually mutates the elements

00:09 <K-ballo> why?

00:09 <gnikunj[m]> because I'm implementing vectors in charm++ and that requires me to work with their version of futures which is giving me some trouble

00:10 <gnikunj[m]> I did find a solution to it now though

00:10 <gnikunj[m]> so the question is more of general cpp knowledge at the moment :D

07:55 <zao> gnikunj[m]: If you're controlling the type and need to access a member in a mutable way in a const context, it's possible that the member should be declared `mutable`.

07:56 <zao> Is the weird old decree that "const means thread-safe" still a thing by the way in the stdlib?

11:01 <gnikunj[m]> zao gotcha

16:43 <tiagofg[m]> Hello,

16:43 <tiagofg[m]> I'm pretend to replicate openMP schedule dynamic in HPX, but I don't know if it's immediate using hpx::for_loop or if I have to add some code around. I saw in your documentation the primitives executor_parameter_traits and hpx::execution::dynamic_chunk_size but I didn't understand how to combine them

17:06 <hkaiser> tiagofg[m]: this test might give you some ideas: https://github.com/STEllAR-GROUP/hpx/blob/master/libs/parallelism/execution/tests/unit/executor_parameters.cpp

17:08 <tiagofg[m]> hkaiser:I think that's it in deed, thanks!