Rust 1.89: What's New, Release History & Support Lifecycle

What Is New in Rust 1.89

How does Rust 1.89 simplify const generic arguments?

Rust 1.89 lets you write an underscore (`_`) as a const generic argument and have the compiler infer the concrete value from surrounding context.

Example:

pub fn all_false<const LEN: usize>() -> [bool; LEN] {
    [false; _]
}

The underscore is resolved to the `LEN` constant, removing boilerplate when the size is already known. This is not allowed in signatures, keeping APIs explicit.

What new lifetime lint does Rust 1.89 introduce and why does it matter?

Rust 1.89 adds the `mismatched_lifetime_syntaxes` lint, which warns when a function's input and output lifetimes belong to different syntactic groups, making hidden lifetimes visible.

Typical warning:

warning: hiding a lifetime that's elided elsewhere is confusing
 --> src/lib.rs:1:18
  |
1 | fn items(scores: &[u8]) -> std::slice::Iter<u8> {
  |                  ^^^^^     -------------------- the same lifetime is hidden here
  |                  |
  |                  the lifetime is elided here
  |
  = help: use `'_` for type paths
  |
1 | fn items(scores: &[u8]) -> std::slice::Iter<'_, u8> {
  |                                             +++

In practice, this reduces confusion for newcomers and helps maintainers spot subtle lifetime bugs early.

Which new SIMD and cryptographic target features are available on x86 in Rust 1.89?

Rust 1.89 expands the `#[target_feature]` attribute to support `sha512`, `sm3`, `sm4`, `kl`, `widekl`, and a broader set of AVX512 features.

Example usage:

#[target_feature(enable = "avx512bw")]
pub fn fast_simd(data: &[u8]) -> Vec {
    // SIMD implementation here
}

Additionally, many AVX512, SHA512, SM3, and SM4 intrinsics are now stable and can be used in const contexts, enabling compile-time computation of cryptographic constants.

How does Rust 1.89 improve cross-compilation and FFI support?

Rust 1.89 adds three key improvements for cross-compilation and foreign-function interfaces.

• Doctests are now executed when you run cargo test --doc --target <other_target>, with the ability to silence platform-specific failures via the `ignore-` annotation.
• `i128` and `u128` no longer trigger the `improper_ctypes_definitions` lint, allowing them in `extern "C"` functions where the platform provides a compatible `__int128` type.
• The `wasm32-unknown-unknown` target now follows the standards-compliant C ABI for `extern "C"` functions, improving interoperability with other languages and toolchains.

These changes reduce friction when targeting embedded or WebAssembly environments and when interfacing with C libraries that require 128-bit integers.

What is the impact of demoting x86_64-apple-darwin to Tier 2 with host tools?

The `x86_64-apple-darwin` target is being moved from Tier 1 to Tier 2, meaning the compiler and standard library will still be built but are no longer guaranteed to pass the full automated test suite.

In practice, most existing macOS builds will continue to work, but CI pipelines that rely on the Tier 1 guarantee may start seeing regressions or missing test coverage. Teams should monitor build logs and be prepared to file bugs if compatibility issues arise.