We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As a trivial example, why we must terminate in the constructor, the following code causes a deadlock if we wait in the destructor.
std::opstream pin: std::ipstream pout; std::process proc{"python", std::process_io(pin, pout)}; throw 42;
The python process will wait for the pipe to close (or the exit command), but the pipe will be closed after the process is destruced.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
As a trivial example, why we must terminate in the constructor, the following code causes a deadlock if we wait in the destructor.
The python process will wait for the pipe to close (or the exit command), but the pipe will be closed after the process is destruced.
The text was updated successfully, but these errors were encountered: