The rust team is happy to announce a new version of RUST, 1.84.0. RUST is a programming language that enables everyone to build reliable and effective programs.
If you have a previous version of RUST installed via rustupYou can get 1.84.0 with:
$ rustup update stable
If you don’t have that already, you can get it rustup From the right page on our website, and verify the detailed version notes for 1.84.0.
If you want to help us by testing future versions, you may consider updating locally to use the beta channel (rustup default beta) Or the night channel (rustup default nightly). Please report any mistakes you may encounter!
What is in 1.84.0 stable
The goods are eating rust versions to choose the dependency version
1.84.0 The minimum subsidized rust version (MSRV) is preferred, which prefers dependency versions compatible with the declared MSRV for the project. With the choice of the MSRV-AWARE version, the toilets are reduced to the warriors to support the old tool chains by not handing the old versions manually for each dependency.
You can subscribe to the MSRV-AWAIN solution .cargo/config.toml:
[resolver]
incompatible-rust-versions = "fallback"
Then when adding dependency:
$ cargo add clap
Updating crates.io index
warning: ignoring [email protected] (which requires rustc 1.74) to maintain demo's rust-version of 1.60
Adding clap v4.0.32 to dependencies
Updating crates.io index
Locking 33 packages to latest Rust 1.60 compatible versions
Adding clap v4.0.32 (available: v4.5.23, requires Rust 1.74)
When checking the latest consequences in CI, you can go beyond this:
$ CARGO_RESOLVER_INCOMPATIBLE_RUST_VERSIONS=allow cargo update
Updating crates.io index
Locking 12 packages to latest compatible versions
Updating clap v4.0.32 -> v4.5.23
You can also subscribe by setting package.resolver = "3" In the Cargo.toml file, although this will require the MSRV upload to 1.84. New solutions will be enabled by projects using the 2024 version (which will settle at 1.85).
This gives library authors more flexibility when determining their policy on adopting new rusting tool features. In the past, the library that relies on features of new rust tools will be forced users in the direction of the river course of that library who have an older rust edition to upgrade their tools or determine an old version of the library compatible with their tools system (and avoid operating cargo update). Now, these users will be able to use old library versions automatically compatible with their old tools.
Review the documents for more considerations when deciding on MSRV policy.
The deportation begins to the permissibility of new features
The programming program for stainlessness is to move to a new application to solve features. Solver of the next generation is a Solver feature a reintegration of a basic component of the RUST system. It is not only responsible for verifying whether the features – for example Vec – A contract, but also uses other parts of the type system, such as normalization – with the discovery of the basic type of T and U It is the same).
In 1.84, a new halal is used to verify the cohesion of the characteristic. At a high level, the cohesion is responsible for ensuring the presence of one application at most of the features of a specific type while thinking about the absence of a written or visible symbol of other boxes.
This installation fixes a few theoretical issues of theoretical in the old implementation, which leads to “conflicting applications of features …” that have not been reported before. We expect the affected patterns to be very rare based on the evaluation of the available code through the hole. The installation also improves our ability to prove that this means that it is no It overlaps, allow more code to write in some cases.
For more details, see a previous blog post and installation report.
Strict source application programming facades
In rust, indicators are not just a “correct number” or “title”. For example, “free use” is an unspecified behavior even if you are “lucky” and the liberated memory is re -customized before reading/writing. Another example, writing through an indicator derived from &i32 The reference is an unspecified behavior, even if writing to the same title through a different indicator is legal. The basic style here is that The way the indicator is calculated with thingsNot only the title that results from this account. For this reason, we say that the indicators have source: To describe the unspecified behavior related to the indicator in rust, we do not only have to know the title that the indicator refers to, but also follow the other indicator (indicators) “derived from”.
Most of the time, programmers do not need to be worried about the original, and it is very clear how the indicator is derived. However, when softening indicators on the correct numbers and return, the resulting indicator is determined. With this version, RUST adds a set of application programming facades that in many cases can replace the uses of a correct number, thus avoiding the ambiguity inherent in such templates.
In particular, the pattern of use of the least parts of the alignment indicator can now be implemented to store additional information without throwing an indicator into a correct number or back. This makes the code easier to think, easier to analyze the translator, as well as the benefits of tools like Miri and the structure such as Cheri that aims to discover and diagnose the misuse of the indicator.
For more details, see the standard library documents on the original.
Stable application programming facades
Ipv6Addr::is_unique_localIpv6Addr::is_unicast_link_localcore::ptr::with_exposed_provenancecore::ptr::with_exposed_provenance_mut::addr ::expose_provenance ::with_addr ::map_addr ::isqrt ::checked_isqrt ::isqrt NonZero::isqrtcore::ptr::without_provenancecore::ptr::without_provenance_mutcore::ptr::danglingcore::ptr::dangling_mutPin::as_deref_mut
These application programming facades are now stable in Const contexts
AtomicBool::from_ptrAtomicPtr::from_ptrAtomicU8::from_ptrAtomicU16::from_ptrAtomicU32::from_ptrAtomicU64::from_ptrAtomicUsize::from_ptrAtomicI8::from_ptrAtomicI16::from_ptrAtomicI32::from_ptrAtomicI64::from_ptrAtomicIsize::from_ptr::is_null ::as_ref ::as_mut Pin::newPin::new_uncheckedPin::get_refPin::into_refPin::get_mutPin::get_unchecked_mutPin::static_refPin::static_mut
Other changes
Check out everything that has changed in rust, goods, and ClipPy.
Contributions in 1.84.0
Many people gathered to create rust 1.84.0. We could not do this without all of you. Thanks!
Rust version team
As published here
Photography by Pablo Gentil on non -earthquakes
