rusty-snake

> Should unknown colors be displayed? As I understand it, if they're not named CSS colors or hex values, they're incorrectly tagged anyway. Code implementing this feature needs to handle...

rust-lang/libc#4400 Merged Released

With libc you mean libc crate? or libc (as in libc.so/glibc/musl)? In the libc crate case, the reason is likely not-yet-implemented. ---- - `capabilities_secure_bits`, `set_capabilities_secure_bits`, `CapabilitiesSecureBits` Can we please rename...

> set_secure_computing_mode does work with SecureComputingMode::Strict +1 > deprecate just SecureComputingMode::Filter This is still a valid return value of `secure_computing_mode()`. And actually the only possible return value of `secure_computing_mode()` other...

> deprecate `secure_computing_mode` `secure_computing_mode` or `set_secure_computing_mode`?

So basically we deprecate `set_secure_computing_mode` and add `set_secure_computing_mode_strict()` and `set_secure_computing_mode_filter(filter, flags)`.

I would just go with ```rust fn set_thread_res_uid(real: R, effective: E, saved_set: S) where R: Into, E: Into, S: Into, ``` This way you can keep passing a Uid directly...

The think is how do we want to implement? 1. `set_thread_res_uid` does `Uid::from_raw_unchecked(-1_i32 as u32)` and `backend::setresuid_thread` is unchanged. 2. `set_thread_res_uid` converts to `RawUid` and `backend::setresuid_thread` takes RawUid. 3. `set_thread_res_uid`...

2. Doesn't sound funny with `ArgReg` 1. Still needs to exploit `from_raw_unchecked(-1_i32 as u32)` So I would go with 3. and `impl`

Ideas for nameing? `child_subreaper2`