You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a very interesting question. I'd imagine fork could send data to each of its following pipes in as many threads? And then the main thread would wait for all to finish?
Tbh I'm not experienced enough with multi-threading to implement this in an optimal manner. I would welcome any suggestion.
Using std::async, the implementation would be really easy. pipes::fork could take an optional policy argument from std::launch and forward it to std::async, or just use std::launch::async. pipes::fork would then either need to return the std::future objects, or wait for them by itself.
Are there any plans to include concurrency? E.g. after a fork...?
The text was updated successfully, but these errors were encountered: