Tracking Issue for `unix_send_signal`
Open
Nobody has claimed this yet.
C-tracking-issue
O-unix
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
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
// std::os::unix::process
pub trait ChildExt {
fn send_signal(&self, signal: i32) -> Result<()>;
fn send_process_group_signal(&self, signal: i32) -> io::Result<()>;
fn kill_process_group(&mut self) -> io::Result<()>;
}
impl ChildExt for std::process::Child { /* ... */ }
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- ACP: https://github.com/rust-lang/libs-team/issues/97
- Incomplete implementation https://github.com/rust-lang/rust/pull/101387
- Implementation: https://github.com/rust-lang/rust/pull/141990
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- Should the signal be an
i32or an enum? Should we provide someSIG*constants so the user doesn't have to depend onlibc? See discussion at the ACP https://github.com/rust-lang/libs-team/issues/97 - Is there some reason our preexisting internal implementation took
&mut? See discussion at https://github.com/rust-lang/rust/pull/141990.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the public API and the ACP at rust-lang/libs-team#97, then review the incomplete and implementation PRs linked in the tracking issue. Resolve the listed questions about the signal type, constants, and mutability, then follow the FCP and stabilization PR steps; done means the feature completes stabilization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100