[ruby-core:101359] [Ruby master Bug#17369] Introduce non-blocking `Process.wait`, `Kernel.system` and related methods.

Issue #17369 has been updated by matz (Yukihiro Matsumoto).


I am OK with `Process::Status.wait`. As far as I've heard the code quality needs upgrade.

Matz.


----------------------------------------
Bug #17369: Introduce non-blocking `Process.wait`, `Kernel.system` and related methods.
https://bugs.ruby-lang.org/issues/17369#change-89066

* Author: ioquatix (Samuel Williams)
* Status: Assigned
* Priority: Normal
* Assignee: ioquatix (Samuel Williams)
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
https://github.com/ruby/ruby/pull/3853

This PR introduces optional hooks to the scheduler interface for handling `Process.wait`, `Kernel.system` and other related methods (`waitpid`, `wait2`, etc).

It funnels all methods through a new interface `Process::Status.wait` which is almost identical to `Process.wait` except for several key differences:

- The return value is a single instance of `Process::Status`.
- It does not set thread local `$?`.

This is necessary for keeping the scheduler interface simple (and side effects are generally bad anyway).



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>