110-------------------
111- [Array coercions may now result in less inference constraints than before](https://github.com/rust-lang/rust/pull/140283)
112▶- Importing `$crate` without renaming, i.e. `use $crate::{self};`, is now no longer permitted due to stricter error checking for `self` imports.
113- [const-eval: be more consistent in the behavior of padding during typed copies.](https://github.com/rust-lang/rust/pull/148967)
114 In very rare cases, this may cause compilation errors due to bytes from parts of a pointer ending up in the padding bytes of a `const` or `static`.
· · ·
114▶ In very rare cases, this may cause compilation errors due to bytes from parts of a pointer ending up in the padding bytes of a `const` or `static`.
115- [A future-incompatibility warning lint `ambiguous_glob_imported_traits` is now reported when using an ambiguously glob imported trait](https://github.com/rust-lang/rust/pull/149058)
116- [Check lifetime bounds of types mentioning only type parameters](https://github.com/rust-lang/rust/pull/149389)
· · ·
117▶- [Report more visibility-related ambiguous import errors](https://github.com/rust-lang/rust/pull/149596)
118- [Deprecate `Eq::assert_receiver_is_total_eq` and emit future compatibility warnings on manual impls](https://github.com/rust-lang/rust/pull/149978)
119- [powerpc64: Use the ELF ABI version set in target spec instead of guessing](https://github.com/rust-lang/rust/pull/150468) (fixes the ELF ABI used by the OpenBSD target)
· · ·
161- [Add warn-by-default `unused_visibilities` lint for visibility on `const _` declarations](https://github.com/rust-lang/rust/pull/147136)
162- [Update to Unicode 17](https://github.com/rust-lang/rust/pull/148321)
163▶- [Avoid incorrect lifetime errors for closures](https://github.com/rust-lang/rust/pull/148329)
164
165<a id="1.94.0-Platform-Support"></a>
· · ·
232 Some finer details of how precise closure captures get affected by pattern matching have been changed. In some cases, this can cause a non-move closure that was previously capturing an entire variable by move, to now capture only part of that variable by move, and other parts by borrow. This can cause the borrow checker to complain where it previously didn't, or cause `Drop` to run at a different point in time.
233- [Standard library macros are now imported via prelude, not via injected `#[macro_use]`](https://github.com/rust-lang/rust/pull/139493)
234▶ This will raise an error if macros of the same name are glob imported.
235 For example if a crate defines their own `matches` macro and then glob imports that,
236 it's now ambiguous whether the custom or standard library `matches` is meant and
+ 364 more matches in this file