kennytm

(@nikomatsakis you can expand the comment, click the "..." then click "Unhide")

to reduce repetition #3444 i.e. putting the inference on the value rather than the type is getting more traction. ```rust // instead of fn rotate(angle: f64) -> _ { let...

The `cfg`-based solution can already be used on nightly with [-Zbuild-std-features](https://doc.rust-lang.org/cargo/reference/unstable.html#build-std-features) like ````sh cargo +nightly build -Zbuild-std=std,panic_abort -Zbuild-std-features=optimize_for_size --target=... ````

I think josh is talking about ```rust impl TryFrom for Arc {} impl TryFrom for Rc {} impl TryFrom for Box {} impl From for Arc {} impl From for...

I think the `Box` impls are not prevented by orphan rules since `Box` is `#[fundamental]`? `Rc` and `Arc` do have problems though.

`Box` workedaround it by implementing the `TryFrom` for `A = Global` only 😅 I tried adding a negative-impl `impl !From for Rc` but all it does is getting rid of...

```rust // Use TryFrom here, because not every owned fd is a valid pipe #[cfg(unix)] impl TryFrom for Fifo { ... } #[cfg(windows)] impl TryFrom for Fifo { ... }...

If we model after `JoinHandle::is_finished` there would be only an `is_initialized() -> bool` function and then > *once this returns true, ~~`join`~~ `force` can be expected to return quickly, without...

> if you see some `x.get()` that tells you jack shit about what's coming next. Except that you can't write `x.get()` in this case, it has to be `LazyLock::get(&x)` and...

Forfeiting method chaining is caused by `LazyLock` implementing `Deref`, it is irrelevant to what the function should be named. Anyway I think it should *not* be called `get`. I expect...