Update Rust to v1.95.0#8093
Conversation
![renovate-approve[bot]](https://avatars.githubusercontent.com/in/7394?s=60&v=4){kind=small}
Merging this PR will not alter performance
|
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ⚡ | Simulation | chunked_varbinview_canonical_into[(1000, 10)] |
197.7 µs | 161.5 µs | +22.41% |
| ❌ | Simulation | chunked_varbinview_opt_canonical_into[(1000, 10)] |
187.4 µs | 225 µs | -16.71% |
| ⚡ | Simulation | density_sweep_random[0.05] |
86.7 µs | 78.2 µs | +10.89% |
| ⚡ | Simulation | patched_take_10k_adversarial |
257.2 µs | 226.7 µs | +13.47% |
| ⚡ | Simulation | patched_take_10k_dispersed |
316.4 µs | 285.7 µs | +10.74% |
| ⚡ | Simulation | patched_take_10k_first_chunk_only |
302.7 µs | 271.9 µs | +11.31% |
| ❌ | Simulation | new_alp_prim_test_between[f32, 32768] |
153.2 µs | 180.9 µs | -15.29% |
| ⚡ | Simulation | take_10k_dispersed |
284.8 µs | 239.3 µs | +19% |
| ⚡ | Simulation | take_10k_first_chunk_only |
271.2 µs | 225.8 µs | +20.1% |
| ⚡ | Simulation | baseline_eq[16, 65536] |
259.6 µs | 228.8 µs | +13.44% |
| ⚡ | Simulation | baseline_eq[4, 65536] |
238.1 µs | 184 µs | +29.41% |
| ⚡ | Simulation | baseline_lt[4, 65536] |
252 µs | 199.2 µs | +26.54% |
| ⚡ | Simulation | baseline_lt[16, 65536] |
274.6 µs | 244 µs | +12.58% |
| ❌ | Simulation | new_alp_prim_test_between[f32, 16384] |
103.9 µs | 117.2 µs | -11.36% |
| ⚡ | Simulation | fsst_prefix[email] |
2.8 ms | 2.4 ms | +16.77% |
| ⚡ | Simulation | fsst_prefix[json] |
3.5 ms | 3.1 ms | +12.64% |
| ⚡ | Simulation | fsst_prefix[path] |
2.8 ms | 2.4 ms | +16.29% |
| ⚡ | Simulation | fsst_prefix[urls] |
3 ms | 2.6 ms | +14.41% |
| ❌ | Simulation | decompress_rd[f32, (100000, 0.1)] |
411.6 µs | 583.5 µs | -29.46% |
| ❌ | Simulation | decompress_rd[f64, (100000, 0.1)] |
667.4 µs | 1,015.8 µs | -34.29% |
| ... | ... | ... | ... | ... | ... |
ℹ️ Only the first 20 benchmarks are displayed. Go to the app to view all benchmarks.
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing renovate/rust-1.x (c612acc) with develop (2699169)
This PR contains the following updates:
1.91.0→1.95.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
rust-lang/rust (rust)
v1.95.0Compare Source
===========================
Language
if letguards on match armsirrefutable_let_patternslint no longer lints on let chainsCompiler
--remap-path-scopefor controlling the scoping of how paths get remapped in the resulting binaryPlatform Support
powerpc64-unknown-linux-muslto Tier 2 with host toolsaarch64-apple-tvosto Tier 2aarch64-apple-tvos-simto Tier 2aarch64-apple-watchosto Tier 2aarch64-apple-watchos-simto Tier 2aarch64-apple-visionosto Tier 2aarch64-apple-visionos-simto Tier 2Refer to Rust's platform support page
for more information on Rust's tiered platform support.
Libraries
thread::scope: document how join interacts with TLS destructorsstr::containson aarch64 targets withneontarget feature enabled by defaultStabilized APIs
MaybeUninit<[T; N]>: From<[MaybeUninit<T>; N]>MaybeUninit<[T; N]>: AsRef<[MaybeUninit<T>; N]>MaybeUninit<[T; N]>: AsRef<[MaybeUninit<T>]>MaybeUninit<[T; N]>: AsMut<[MaybeUninit<T>; N]>MaybeUninit<[T; N]>: AsMut<[MaybeUninit<T>]>[MaybeUninit<T>; N]: From<MaybeUninit<[T; N]>>Cell<[T; N]>: AsRef<[Cell<T>; N]>Cell<[T; N]>: AsRef<[Cell<T>]>Cell<[T]>: AsRef<[Cell<T>]>bool: TryFrom<{integer}>AtomicPtr::updateAtomicPtr::try_updateAtomicBool::updateAtomicBool::try_updateAtomicIn::updateAtomicIn::try_updateAtomicUn::updateAtomicUn::try_updatecfg_select!mod core::rangecore::range::RangeInclusivecore::range::RangeInclusiveItercore::hint::cold_path<*const T>::as_ref_unchecked<*mut T>::as_ref_unchecked<*mut T>::as_mut_uncheckedVec::push_mutVec::insert_mutVecDeque::push_front_mutVecDeque::push_back_mutVecDeque::insert_mutLinkedList::push_front_mutLinkedList::push_back_mutLayout::dangling_ptrLayout::repeatLayout::repeat_packedLayout::extend_packedThese previously stable APIs are now stable in const contexts:
fmt::from_fnControlFlow::is_breakControlFlow::is_continueRustdoc
Compatibility Notes
$cratewithout renaming, i.e.use $crate::{self};, is now no longer permitted due to stricter error checking forselfimports.In very rare cases, this may cause compilation errors due to bytes from parts of a pointer ending up in the padding bytes of a
constorstatic.ambiguous_glob_imported_traitsis now reported when using an ambiguously glob imported traitEq::assert_receiver_is_total_eqand emit future compatibility warnings on manual impls#[non_exhaustive]enum now reads the discriminant, even if the enum has only one variant. This can cause closures to capture values that they previously wouldn't.mut refandmut ref mutpatterns, part of the unstable Match Ergonomics 2024 RFC, were accidentally allowed on stable within struct pattern field shorthand. These patterns are now correctly feature-gated as unstable in this position.-Z unstable-optionsto use. Previously, they could not be used without the standard library, which has no stable build mechanism. In preparation for thebuild-stdproject adding that support, JSON target specs are being proactively gated to ensure they remain unstable even ifbuild-stdis stabilized. Cargo now includes the-Z json-target-specCLI flag to automatically pass-Z unstable-optionsto the compiler when needed. See #150151, #151534, and rust-lang/cargo#16557.#[feature]attributes on invalid targets are now checkedInternal Changes
These changes do not affect any public interfaces of Rust, but they represent
significant improvements to the performance or internals of rustc and related
tools.
v1.94.1Compare Source
===========================
std::thread::spawnon wasm32-wasip1-threadsstd::os::windows::fs::OpenOptionsExtThe new methods were unstable, but the trait itself is not sealed and so
cannot be extended with non-default methods.
match_same_armsThis resolves CVE-2026-33055 and CVE-2026-33056. Users of crates.io are not affected.
See blog for more details.
v1.94.0Compare Source
==========================
Language
dead_codelint level of the corresponding traits and trait itemsunused_visibilitieslint for visibility onconst _declarationsPlatform Support
riscv64im-unknown-none-elfas a tier 3 targetRefer to Rust's platform support page
for more information on Rust's tiered platform support.
Libraries
T: Ordbound for someBinaryHeap<T>methods.Stabilized APIs
<[T]>::array_windows<[T]>::element_offsetLazyCell::getLazyCell::get_mutLazyCell::force_mutLazyLock::getLazyLock::get_mutLazyLock::force_mutimpl TryFrom<char> for usizestd::iter::Peekable::next_if_mapstd::iter::Peekable::next_if_map_mutavx512fp16intrinsics(excluding those that depend directly on the unstable
f16type)(excluding those that depend directly on the unstable
f16type)f32::consts::EULER_GAMMAf64::consts::EULER_GAMMAf32::consts::GOLDEN_RATIOf64::consts::GOLDEN_RATIOThese previously stable APIs are now stable in const contexts:
f32::mul_addf64::mul_addCargo
CARGO_BIN_EXE_<crate>available at runtimeCompatibility Notes
dyn-typesSome finer details of how precise closure captures get affected by pattern matching have been changed. In some cases, this can cause a non-move closure that was previously capturing an entire variable by move, to now capture only part of that variable by move, and other parts by borrow. This can cause the borrow checker to complain where it previously didn't, or cause
Dropto run at a different point in time.#[macro_use]This will raise an error if macros of the same name are glob imported.
For example if a crate defines their own
matchesmacro and then glob imports that,it's now ambiguous whether the custom or standard library
matchesis meant andan explicit import of the name is required to resolve the ambiguity.
One exception is
core::panicandstd::panic, if their import is ambiguousa new warning (
ambiguous_panic_imports) is raised.This may raise a new warning (
ambiguous_panic_imports) on#![no_std]code glob importing the std crate.Both
core::panic!andstd::panic!are then in scope and which is used is ambiguous.include!(…)sThis can cause previously working includes to no longer compile if they included files which started with a shebang.
This unifies behavior between local and cross-crate errors on these exports, which may introduce new ambiguity errors.
These attributes currently have no effect in this position.
std::time::SystemTime::checked_sub_durationwill returnNonefor times before the Windows epoch (1/1/1601)'aare now NFC normalized.Any paths emitted by compiler now always respect the relative-ness of the paths and
--remap-path-prefixgiven originally.One side-effect of this change is that paths emitted for local crates in Cargo (path dependencies and workspace members) are no longer absolute but relative when emitted as part of a diagnostic in a downstream crate.
Internal Changes
These changes do not affect any public interfaces of Rust, but they represent
significant improvements to the performance or internals of rustc and related
tools.
annotate-snippetsfor error emissionThis should preserve mostly the same outputs in rustc error messages.
v1.93.1Compare Source
===========================
clippy::panicking_unwrapfalse-positive on field access with implicit deref.wasm32-wasip2target.v1.93.0Compare Source
==========================
Language
vector-related target features and theis_s390x_feature_detected!macrosystemABIcfgpredicateasm_cfgconstitems that contain mutable references tostatic(which is very unsafe, but not always UB)const_item_interior_mutationslint to warn against calls which mutate interior mutableconstitemsfunction_casts_as_integerlintCompiler
-Cjump-tables=bool. The flag was previously called-Zno-jump-tables.Platform Support
riscv64a23-unknown-linux-gnuto Tier 2 (without host tools)Refer to Rust's platform support page
for more information on Rust's tiered platform support.
Libraries
specializationon theCopytrait as it is unsound in the presence of lifetime dependentCopyimplementations. This may result in some performance regressions as some standard library APIs may now callClone::cloneinstead of performing bitwise copiesstd::thread::current()BTree::appendnot update existing keys when appending an entry which already existsT: RefUnwindSafeforvec::IntoIter<T>: UnwindSafeStabilized APIs
<[MaybeUninit<T>]>::assume_init_drop<[MaybeUninit<T>]>::assume_init_ref<[MaybeUninit<T>]>::assume_init_mut<[MaybeUninit<T>]>::write_copy_of_slice<[MaybeUninit<T>]>::write_clone_of_sliceString::into_raw_partsVec::into_raw_parts<iN>::unchecked_neg<iN>::unchecked_shl<iN>::unchecked_shr<uN>::unchecked_shl<uN>::unchecked_shr<[T]>::as_array<[T]>::as_mut_array<*const [T]>::as_array<*mut [T]>::as_mut_arrayVecDeque::pop_front_ifVecDeque::pop_back_ifDuration::from_nanos_u128char::MAX_LEN_UTF8char::MAX_LEN_UTF16std::fmt::from_fnstd::fmt::FromFnCargo
cargo tree, support long forms for--formatvariables--workspacetocargo cleanRustdoc
#![doc(document_private_items)]importhtml_favicon_url,html_logo_url,html_playground_url,issue_tracker_base_url, orhtml_no_sourceeither has a missing value, an unexpected value, or a value of the wrong type, rustdoc will emit the deny-by-default lintrustdoc::invalid_doc_attributes.Compatibility Notes
pin_v2into the builtin attributes namespacepanic=unwindwas changed from the JS exception handling ABI to the wasm exception handling ABI. If linking C/C++ object files with Rust objects,-fwasm-exceptionsmust be passed to the linker now. On nightly Rust, it is possible to get the old behavior with-Zwasm-emscripten-eh=false -Zbuild-std, but it will be removed in a future release.#[test]attribute, used to define tests, was previously ignored in various places where it had no meaning (e.g on trait methods or types). Putting the#[test]attribute in these places is no longer ignored, and will now result in an error; this may also result in errors when generating rustdoc. Error whentestattribute is applied to structsCARGO_CFG_DEBUG_ASSERTIONSenvironment variable in more situations. This will cause crates depending onstatic-initversions 1.0.1 to 1.0.3 to fail compilation with "failed to resolve: use of unresolved module or unlinked crateparking_lot". See the linked issue for details.offset_of!macro are now checked to be well formed.cargo publishno longer emits.cratefiles as a final artifact for user access when thebuild.build-dirconfig is unsetderef_nullptrlint from warn-by-default to deny-by-default...function parameters without a pattern outside ofexternblocksrepr(C)enums whose discriminant values do not fit into ac_intorc_uintrepr(C)types as part ofrepr(transparent)v1.92.0Compare Source
==========================
Language
MaybeUninitrepresentation and validity&raw [mut | const]for union field in safe codeSizedXin[X; 0]whenXis unsizing a const#[track_caller]and#[no_mangle](requires every declaration specifying#[track_caller]as well)never_type_fallback_flowing_into_unsafeanddependency_on_unit_never_type_fallbackdeny-by-defaultunused_must_uselint no longer warns onResult<(), Uninhabited>(for instance,Result<(), !>), orControlFlow<Uninhabited, ()>. This avoids having to check for an error that can never happen.Compiler
mips64el-unknown-linux-muslabi64link dynamicallyCommand-line information is typically not needed by debugging tools, and the removed code
was causing problems for incremental builds even on targets that don't use PDB debuginfo.
Libraries
Iterator::eq{_by}forTrustedLeniteratorsExtendfor tuplesDebugforEncodeWide.iter::Repeat::lastandcountwill now panic, rather than looping infinitely.Stabilized APIs
NonZero<u{N}>::div_ceilLocation::file_as_c_strRwLockWriteGuard::downgradeBox::new_zeroedBox::new_zeroed_sliceRc::new_zeroedRc::new_zeroed_sliceArc::new_zeroedArc::new_zeroed_slicebtree_map::Entry::insert_entrybtree_map::VacantEntry::insert_entryimpl Extend<proc_macro::Group> for proc_macro::TokenStreamimpl Extend<proc_macro::Literal> for proc_macro::TokenStreamimpl Extend<proc_macro::Punct> for proc_macro::TokenStreamimpl Extend<proc_macro::Ident> for proc_macro::TokenStreamThese previously stable APIs are now stable in const contexts:
<[_]>::rotate_left<[_]>::rotate_rightCargo
Rustdoc
Iterator::lastas well as impl methods likestd::vec::IntoIter::last. Now these impl methods will be hidden, freeing up space for inherent methods likeBTreeSet::last.Compatibility Notes
-C panic=aborton Linux by generating unwind tables by default. Build with-C force-unwind-tables=noto keep omitting unwind tables.invalid_macro_export_argumentsis upgraded to deny-by-default and will be reported in dependencies too.impl DerefMut for Pin<LocalType>pin!and formatting macrosv1.91.1Compare Source
===========================
wasm_import_moduleattribute cross-crate. This fixes linker errors on WASM targets.Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.