rust-lang / rust-lang/rust

Tracking Issue for `unix_send_signal`

Open
#141,975 4 comments 2 reactions 0 assignees View on GitHub

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.)

Unresolved Questions

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.