Skip to content

Rust 1.98.1: full best-practices refresh #9

Closed

Description

@codeandsolder

Rust 1.98.1 is the current stable toolchain.

Do a complete repository refresh against Rust 1.98.0/1.98.1 rather than only replacing a toolchain version:

  • Read the official Rust 1.98.0 and 1.98.1 announcements and detailed release notes/changelog.
  • Review relevant language, standard-library, rustc, Cargo, Clippy, rustfmt, target/platform, and tooling changes.
  • Review all Rust code, Cargo.toml/Cargo.lock, CI, Docker/build tooling, SKILL.md, README/docs, examples, lints, and project conventions for newly preferable patterns or obsolete workarounds.
  • Adopt useful newly-stable features and current best practices where they improve the project; remove workarounds that current stable makes unnecessary.
  • Keep the intentional MSRV contract separate unless there is a separately justified reason to raise it.
  • Run the full CI-equivalent test matrix and fix fallout.
  • If current stable is already fully reflected, document what was reviewed and close this issue as a no-op.

Generated as the initial queue item for the passive stable-Rust maintenance workflow.

Activity

  1. codeandsolder commented on Sep 9, 2026

    @codeandsolder
    OwnerAuthor

    No-op after full 1.98.0/1.98.1 review: this queue item was generated after the relevant modernization had already merged in #8 (merge commit d40832f).

    Reviewed against the official Rust 1.98.0 release notes and the 1.98.1 point-release advisory. #8 already moved current development/CI/builds to patched 1.98.1 while preserving the Rust 1.94 MSRV, adopted resolver 3 for the virtual 2024-edition workspace, adopted Cargo-native CARGO_BUILD_WARNINGS=deny, and changed the WASM current-stable lane from cargo check to a real link to cover the post-1.96 wasm-ld behavior. rust-toolchain.toml is already pinned to 1.98.1.

    The newly stabilized 1.98 APIs (NumBuffer/integer format_into, algebraic floating-point methods, substr_range/subslice_range, UTF-16 endian constructors, atomic slice helpers, etc.) do not correspond to an existing workaround or dependency in this workspace that should be mechanically replaced. The 1.98.1 vtable miscompilation is addressed by the existing 1.98.1 pin. No additional repository change is justified for this release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions