-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
Tracking Issue for unix_send_signal #141975
Copy link
Copy link
Open
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCO-unixOperating system: Unix-likeOperating system: Unix-likeT-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.
Metadata
Metadata
Assignees
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCO-unixOperating system: Unix-likeOperating system: Unix-likeT-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Feature gate:
#![feature(unix_send_signal)]This is a tracking issue for API to send a signal to a child process via libc
kill.Public API
Steps / History
(Remember to update the
S-tracking-*label when checking boxes.)interruptfunction tostd::process::Childlibs-team#97interruptfunction forstd::process::Child#101387Unresolved Questions
i32or an enum? Should we provide someSIG*constants so the user doesn't have to depend onlibc? See discussion at the ACP Addinterruptfunction tostd::process::Childlibs-team#97&mut? See discussion at Implement send_signal for unix child processes #141990.Footnotes
https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩