|
| 1 | +Version 1.93.1 (2026-02-12) |
| 2 | +=========================== |
| 3 | + |
| 4 | +<a id="1.93.1"></a> |
| 5 | + |
| 6 | +- [Don't try to recover keyword as non-keyword identifier](https://github.com/rust-lang/rust/pull/150590), fixing an ICE that especially [affected rustfmt](https://github.com/rust-lang/rustfmt/issues/6739). |
| 7 | +- [Fix `clippy::panicking_unwrap` false-positive on field access with implicit deref](https://github.com/rust-lang/rust-clippy/pull/16196). |
| 8 | +- [Revert "Update wasm-related dependencies in CI"](https://github.com/rust-lang/rust/pull/152259), fixing file descriptor leaks on the `wasm32-wasip2` target. |
| 9 | + |
1 | 10 | Version 1.93.0 (2026-01-22) |
2 | 11 | ========================== |
3 | 12 |
|
@@ -1546,7 +1555,7 @@ Compatibility Notes |
1546 | 1555 | - [Check well-formedness of the source type's signature in fn pointer casts.](https://github.com/rust-lang/rust/pull/129021) This partly closes a soundness hole that comes when casting a function item to function pointer |
1547 | 1556 | - [Use equality instead of subtyping when resolving type dependent paths.](https://github.com/rust-lang/rust/pull/129073) |
1548 | 1557 | - Linking on macOS now correctly includes Rust's default deployment target. Due to a linker bug, you might have to pass `MACOSX_DEPLOYMENT_TARGET` or fix your `#[link]` attributes to point to the correct frameworks. See <https://github.com/rust-lang/rust/pull/129369>. |
1549 | | -- [Rust will now correctly raise an error for `repr(Rust)` written on non-`struct`/`enum`/`union` items, since it previous did not have any effect.](https://github.com/rust-lang/rust/pull/129422) |
| 1558 | +- [Rust will now correctly raise an error for `repr(Rust)` written on non-`struct`/`enum`/`union` items, since it previously did not have any effect.](https://github.com/rust-lang/rust/pull/129422) |
1550 | 1559 | - The future incompatibility lint `deprecated_cfg_attr_crate_type_name` [has been made into a hard error](https://github.com/rust-lang/rust/pull/129670). It was used to deny usage of `#![crate_type]` and `#![crate_name]` attributes in `#![cfg_attr]`, which required a hack in the compiler to be able to change the used crate type and crate name after cfg expansion. |
1551 | 1560 | Users can use `--crate-type` instead of `#![cfg_attr(..., crate_type = "...")]` and `--crate-name` instead of `#![cfg_attr(..., crate_name = "...")]` when running `rustc`/`cargo rustc` on the command line. |
1552 | 1561 | Use of those two attributes outside of `#![cfg_attr]` continue to be fully supported. |
@@ -1722,7 +1731,7 @@ Cargo |
1722 | 1731 | Compatibility Notes |
1723 | 1732 | ------------------- |
1724 | 1733 | - We now [disallow setting some built-in cfgs via the command-line](https://github.com/rust-lang/rust/pull/126158) with the newly added [`explicit_builtin_cfgs_in_flags`](https://doc.rust-lang.org/rustc/lints/listing/deny-by-default.html#explicit-builtin-cfgs-in-flags) lint in order to prevent incoherent state, eg. `windows` cfg active but target is Linux based. The appropriate [`rustc` flag](https://doc.rust-lang.org/rustc/command-line-arguments.html) should be used instead. |
1725 | | -- The standard library has a new implementation of `binary_search` which is significantly improves performance ([#128254](https://github.com/rust-lang/rust/pull/128254)). However when a sorted slice has multiple values which compare equal, the new implementation may select a different value among the equal ones than the old implementation. |
| 1734 | +- The standard library has a new implementation of `binary_search` which significantly improves performance ([#128254](https://github.com/rust-lang/rust/pull/128254)). However when a sorted slice has multiple values which compare equal, the new implementation may select a different value among the equal ones than the old implementation. |
1726 | 1735 | - [illumos/Solaris now sets `MSG_NOSIGNAL` when writing to sockets](https://github.com/rust-lang/rust/pull/128259). This avoids killing the process with SIGPIPE when writing to a closed socket, which matches the existing behavior on other UNIX targets. |
1727 | 1736 | - [Removes a problematic hack that always passed the --whole-archive linker flag for tests, which may cause linker errors for code accidentally relying on it.](https://github.com/rust-lang/rust/pull/128400) |
1728 | 1737 | - The WebAssembly target features `multivalue` and `reference-types` are now |
@@ -1872,7 +1881,7 @@ These changes do not affect any public interfaces of Rust, but they represent |
1872 | 1881 | significant improvements to the performance or internals of rustc and related |
1873 | 1882 | tools. |
1874 | 1883 |
|
1875 | | -- [Add a Rust-for Linux `auto` CI job to check kernel builds.](https://github.com/rust-lang/rust/pull/125209/) |
| 1884 | +- [Add a Rust-for-Linux `auto` CI job to check kernel builds.](https://github.com/rust-lang/rust/pull/125209/) |
1876 | 1885 |
|
1877 | 1886 | Version 1.80.1 (2024-08-08) |
1878 | 1887 | =========================== |
@@ -4510,7 +4519,7 @@ Compatibility Notes |
4510 | 4519 | saturating to `0` instead][89926]. In the real world the panic happened mostly |
4511 | 4520 | on platforms with buggy monotonic clock implementations rather than catching |
4512 | 4521 | programming errors like reversing the start and end times. Such programming |
4513 | | - errors will now results in `0` rather than a panic. |
| 4522 | + errors will now result in `0` rather than a panic. |
4514 | 4523 | - In a future release we're planning to increase the baseline requirements for |
4515 | 4524 | the Linux kernel to version 3.2, and for glibc to version 2.17. We'd love |
4516 | 4525 | your feedback in [PR #95026][95026]. |
|
0 commit comments