Why does drop()ing a process::Child no longer wait() on it?

help
#1

Anyone know the specific reason why std::process::Child doesn't wait() on drop()?

Digging through through though the source I see that early on it did wait, and when an RFC was created to replace old_io, it mentions forget() remaining the same (which was the old way of opting in to not waiting):

But when the PR that actually implemented it went in, Drop was removed without comment

I know that this is extensively documented and I could just write a wrapper type myself, but it feels strange that such a decision occurred without discussion. Does anyone know where this conversation might have happened, if it did?

#2

Shot in the dark, but @aturon?

#3

This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.