//! Owner-death containment for this process (macos).
use crate;
/// macOS has no parent-death signal and no job objects.
///
/// Reporting that plainly is the useful answer: the caller must spawn a
/// supervisor that watches the owner and does the reaping itself. Returning
/// `Unsupported` here would say "nothing can be done", which is false and
/// would lose the containment the supervisor provides.
/// What this host will attempt, without attempting it.
/// What binding a child to *this* process's lifetime obtains here.
///
/// The spawn path forks a kqueue supervisor before `exec` and waits for its
/// owner and child watches to be registered before reporting spawn success,
/// so the containment is real -- but it is a user-space process doing the
/// reaping, and nothing reaps if that supervisor is killed too. This host has
/// no parent-death signal and no job objects, and saying so is the useful
/// answer: a caller needing a guarantee that survives losing every user-space
/// participant has to refuse here rather than assume.