C++11: Future Chaining For Easy, Highly Threaded Execution

cassandravoiton · 21 days

Thanks for pointing that out - fixed a few.

cassandravoiton · 21 days

Try replacing the spinning loop with a wait:

this_thread::sleep_for(chrono::seconds(1));

The effects are quite interesting as you get to see the size of the underlying thread pool.

Andrey_Karpov_N · 1 month

If you use pointers rather than references, IE the vector is a vector of pointers and you pass the pointers around, you don't get the problem. Storing a vector of non trivial items (rather than pointers to them) is likely to cause problems.

code-dog · 2 months

Yes but that does not fix all cases. Sometimes you might neex to have multiple ownership which cannot be resolved at compile time.

code-dog · 2 months

You are right except that the code comes from a bigger project where all types which were legal in the implementation of the dsl were typedef so it was consistent and thus easier to code.

code-dog · 2 months

That is what I siad so I guess I agree with you.

code-dog · 2 months

Why?

code-dog · 2 months

not a bad idea, but it requires more work. How about just making a version of counted_ptr which uses intrusive_ptr.

nerds-central

TROPHY CASE

nerds-central

TROPHY CASE

you'll need to login or register to do that

create a new account

login