A future Rust version will add core::range::RangeFull and core::range::RangeTo as re-exports from core::ops. These do not implement Iterator and already implement Copy, the Rust team said. A future Rust version will also introduce core::range::legacy::* as the new home for the current ranges. Range syntax like 0..1 still produces the legacy types for now, the Rust team said, but will be updated to core::range types in an upcoming edition. With these stabilizations, it is now possible to store slice accessors in Copy types without splitting start and end, according to the team. Additionally, the new RangeInclusive type makes its fields public, unlike the legacy version that avoided exposing the exhausted iterator state.
Elsewhere in Rust 1.96.0, two new macros, assert_matches! and debug_assert_matches!, check that a value matches a given pattern, panicking with a Debug representation of the value otherwise. And WebAssembly targets no longer pass --allow-undefined to the linker, which means that undefined symbols when linking are now a linker error instead of being converted to WebAssembly imports from the "env" module. This change prevents modules from linking unless all linking-related symbols are defined to catch bugs earlier and prevent accidental issues with symbol naming or similar.
The Rust team on June 30 published a point release, Rust 1.96.1, which offers a series of fixes for Cargo, MIR, and libssh2:
