Skip to content

Commit 7f10299

Browse files
authored
Add missing entries in 1.74 release notes
1 parent 49b27f4 commit 7f10299

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

RELEASES.md

+2
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,7 @@ Language
1212
- [Allow explicit `#[repr(Rust)]`](https://github.com/rust-lang/rust/pull/114201/)
1313
- [closure field capturing: don't depend on alignment of packed fields](https://github.com/rust-lang/rust/pull/115315/)
1414
- [Enable MIR-based drop-tracking for `async` blocks](https://github.com/rust-lang/rust/pull/107421/)
15+
- [Stabilize `impl_trait_projections`](https://github.com/rust-lang/rust/pull/115659)
1516

1617
<a id="1.74.0-Compiler"></a>
1718

@@ -101,6 +102,7 @@ Compatibility Notes
101102
- [make Cell::swap panic if the Cells partially overlap](https://github.com/rust-lang/rust/pull/114795/)
102103
- [Reject invalid crate names in `--extern`](https://github.com/rust-lang/rust/pull/116001/)
103104
- [Don't resolve generic impls that may be shadowed by dyn built-in impls](https://github.com/rust-lang/rust/pull/114941/)
105+
- [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.
104106

105107
<a id="1.74.0-Internal-Changes"></a>
106108

0 commit comments

Comments
 (0)