Jacob Lifshay

some notes on `POSIX_SPAWN_CLOEXEC_DEFAULT`: https://github.com/python/cpython/issues/109154 also, apparently when adding explicitly inherited file descriptors using `posix_spawn_file_actions_addinherit_np` they must be less than `OPEN_MAX`: https://github.com/joyent/libuv/issues/1483

it might be a good idea to instead require an empty block (or maybe `! => !,` where `!` is an expression -- a constructor for the `!` type that...

I think allowing `.await` in format arguments is a bad idea because `.await` commonly has highly non-trivial side effects that are obscured by being in a format string, `Deref` isn't...

> With `Deref`, there is the chance of interior mutability being exploited, and this can definitely result in some unexpected errors. this is exactly the same as accessing interior mutability...

> ```rust > println!("Hello {(match self.pref(person) { > Pref::Like => "friend", > Pref::Neutral => "there", > Pref::Dislike => "you piece of trash" > })}!"); > ``` Unless Rust added something...

> I also have to disagree that this isn't useful on its own, I come across uses quite frequently in projects that use a lot of statics (e.g. modular C+Rust...

> I think maybe it is best to leave thta under unresolved questions or future possibilities for now, since more information will probably become apparent at implementation time. I'll update...

> There's an important note about performance. Because `Path` is not represented as `CString` / `OsString`, every operation which can fail with path-related error already has to allocate on the...

> 1. Provide a `Complex` type which is FFI-compatible with C's `_Complex T` at least for `T = f32`, `f64`, and exposes [all methods available in C](https://en.cppreference.com/w/c/numeric/complex.html), or > 2....

> If the motivation for putting it in std is just for FFI, could the std one just be a struct with pub fields and no otger API, and then...