Repository navigation
Confusion about UseHandle handles being closed. #2
Description
Activity
Initial description was empty, I've edited the description to contain the desired content.
I'm looking at the
processcode right now and was puzzled by the very same thing. While there are probably many situations where you want the handles to be closed, I don't see how this is universally true.If there aren't any serious objections to the proposal on the libraries@ list this week, I'll send a pull request on Sunday for this.
so... is this issue resolved now?
Yes, thank you.
- added a commit that references this issue
on May 4, 2026
Sorry for initial empty description...
When working on a library, I was surprised to find that the
Handles that I passed in forstd_in,std_outandstd_errviaUseHandlewere automatically closed. This is not clear from the documentation, and- at least for the use case I was interested in- the opposite of what I needed. There are valid cases where we'd want theHandleto remain open after the process runs to completion.The function
createProcess_in the.Internalsmodule has the behavior I was looking for, and for my purpose, I can simply import from there. I'd like to propose two changes:createProcessindicating that it will close theHandleautomatically.System.Processwith the semantics ofcreateProcess_. I'm open to bikeshedding on the name, but perhaps sticking withcreateProcess_makes the most sense.Note that I do not think we should change the existing semantics of
createProcess: I think it's a large breaking change, and should be avoided.I'm happy to provide pull requests for both of these, I just wanted to check if there was objection before going ahead with it.