kennytm

That `impl` is only possible within the crate that defines `Bar`. And when using `NonNull::::from` the only case you are going to accidentally invoke that `impl` only if the type...

for reference OP submitted an actual RFC at #3604.

well, for one, those dedicated traits are already proposed in other RFCs 🙃 (AsRepr, FromRepr @ rust-lang/rust#86772 ← #3040, #3046, *not yet implemented*)

> then perform `?` operator on that to return early The problem being that `expr?` is not a valid [*place*](https://doc.rust-lang.org/reference/expressions.html#place-expressions-and-value-expressions), so if you treat `x[y]_` and `x?` as independent constructs...

The `Try` trait can't produce any "place" either. Unless you want it to return an `&mut X` on success and make the lowering *implicitly dereference* the Try result. ```rust let...

chained `?` is already a valid syntax ([and used in real code](https://github.com/actix/actix-web/blob/ba7bddeadc30a40c1e0a53049c3f726f0f661f4d/awc/src/client/h1proto.rs#L93)), you can't repurpose `??` to mean anything else. ```rust fn lol(huh: Option) -> Option { huh???? } ```

you can get a library function into std faster through the ACP process https://std-dev-guide.rust-lang.org/development/feature-lifecycle.html#suitability-for-the-standard-library. ---- anyway what is the use case for this not covered by `format!("{:.2}", full_float)`?

if you need to be interoperate with Python do note that Rust's rounding result might not be the same as that of Python. | Number | 0.05 | 0.15 |...

Since this `use` thing is part of the type signature, could you clarify if the capture list is changed, when it will be considered breaking change or not? From the...

> ```rust > // Y = ::Item. > // Are we allowed to capture A now that it appears in a projection type? > // I don't think so since...