Announcing Rust 1.61.0

This page summarizes the projects mentioned and recommended in the original post on reddit.com/r/rust

Our great sponsors
  • SonarLint - Clean code begins in your IDE with SonarLint
  • Scout APM - Less time debugging, more time building
  • SaaSHub - Software Alternatives and Reviews
  • rust

    Empowering everyone to build reliable and efficient software.

    In general I agree with this but that is not the reason there are two separate functions here. The discussions here and here seem to have come to the conclusion that retain_mut is being added as a backwards compatible fix for retain.

  • Cargo

    The Rust package manager

    Anybody knows when cargo-add will be distributed in stable cargo? Seems merged already.

  • SonarLint

    Clean code begins in your IDE with SonarLint. Up your coding game and discover issues early. SonarLint is a free plugin that helps you find & fix bugs and security issues from the moment you start writing code. Install from your favorite IDE marketplace today.

  • rfcs

    RFCs for changes to Rust

    This is one of the eventual goals of the unstable provide_any feature, which will allow (among other things) adding additional optional APIs to dyn Error. See also the related RFC 2895, the author of which notes explicitly:

  • compiler-team

    A home for compiler team planning documents, meeting minutes, and other such things.

    From https://github.com/rust-lang/compiler-team/issues/493

  • unsafe-code-guidelines

    Home for the Unsafe Code Guidelines working group.

    // SAFETY: The `add` here is safe, because: // // - Both pointers are part of the same object, as pointing directly // past the object also counts. // // - The size of the slice is never larger than isize::MAX bytes, as // noted here: // - https://github.com/rust-lang/unsafe-code-guidelines/issues/102#issuecomment-473340447 // - https://doc.rust-lang.org/reference/behavior-considered-undefined.html // - https://doc.rust-lang.org/core/slice/fn.from_raw_parts.html#safety // (This doesn't seem normative yet, but the very same assumption is // made in many places, including the Index implementation of slices.) // // - There is no wrapping around involved, as slices do not wrap past // the end of the address space.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts