Skip to content

refactor: I/O safety for add_open and add_dup2 #2588

New issue

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

Closed
wants to merge 2 commits into from

Conversation

tisonkun
Copy link
Contributor

@tisonkun tisonkun commented Jan 27, 2025

What does this PR do

According to #2579 (comment).

cc @SteveLauC please check if this PR follows your expectation.

Checklist:

  • I have read CONTRIBUTING.md
  • I have written necessary tests and rustdoc comments
  • A change log has been added if this PR modifies nix's API

@tisonkun tisonkun changed the title refactor: I/O safety for add_dup2 refactor: I/O safety for add_open and add_dup2 Jan 27, 2025
Signed-off-by: tison <[email protected]>
@SteveLauC
Copy link
Member

Sorry for the late reply!

The first PR #2475 that added posix_spawn() to Nix actually adopted I/O-safety, then a following PR #2491 removed it because I/O-safety does not make too much sense here

@tisonkun
Copy link
Contributor Author

tisonkun commented Feb 7, 2025

So it's not part of the release blocker?

If so, feel free to close this PR

@SteveLauC
Copy link
Member

So it's not part of the release blocker?

Yeah

Close the PR then

@SteveLauC SteveLauC closed this Feb 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants