Apply suggestions from code review

Co-authored-by: Slanterns <[email protected]>
Co-authored-by: Josh Stone <[email protected]>

Author: 3 people

RELEASES.md

@@ -11,6 +11,7 @@ Language
   Read more in [RFC 2145](https://rust-lang.github.io/rfcs/2145-type-privacy.html).
 - [Allow explicit `#[repr(Rust)]`](https://github.com/rust-lang/rust/pull/114201/)
 - [closure field capturing: don't depend on alignment of packed fields](https://github.com/rust-lang/rust/pull/115315/)
+- [Stabilize `impl_trait_projections`](https://github.com/rust-lang/rust/pull/115659)
 
 <a id="1.74.0-Compiler"></a>
 
@@ -65,6 +66,7 @@ Compatibility Notes
 - [Raise minimum supported Apple OS versions](https://github.com/rust-lang/rust/pull/104385/)
 - [make Cell::swap panic if the Cells partially overlap](https://github.com/rust-lang/rust/pull/114795/)
 - [Reject invalid crate names in `--extern`](https://github.com/rust-lang/rust/pull/116001/)
+- [The new `impl From<{&,&mut} [T; N]> for Vec<T>` is known to cause some inference failures with overly-generic code.](https://github.com/rust-lang/rust/issues/117054) In those examples using the `tui` crate, the combination of `AsRef<_>` and `Into<Vec>` leaves the middle type ambiguous, and the new `impl` adds another possibility, so it now requires an explicit type annotation.
 
 <a id="1.74.0-Internal-Changes"></a>