chore(deps): update dependency rust to 1.98 - #355
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
added
custom
dependencies
|
Bundle ReportBundle size has no change ✅ |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #355 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 6 6
Lines 177 177
Branches 47 47
=========================================
Hits 177 177 Continue to review full report in Codecov by Harness.
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.91→1.98Release Notes
rust-lang/rust (rust)
v1.98.1Compare Source
===========================
v1.98.0Compare Source
==========================
Language
&mutwhen unsize-coercing, even in an invariant position. For example, you can now coerce aCell<&'long mut i32>to aCell<&'short mut dyn Send>. Such shortenings were already previously allowed when coercing a&mutto a&, or coercing a&to a&.invalid_runtime_symbol_definitionslint and warn-by-defaultsuspicious_runtime_symbol_definitionslintcoreruntime symbols likememcmp,memset,strlen, ... and is planned to be expanded in the next few releases.c_void_returnslint to checkcore::ffi::c_voidas a return typePlatform Support
powerpc64-unknown-linux-gnuelfv2as Tier 3aarch64-unknown-linux-pauthtestas Tier 3 targetthumbv7a-none-eabito Tier 2thumbv7a-none-eabihfto Tier 2thumbv7r-none-eabito Tier 2thumbv7r-none-eabihfto Tier 2thumbv8r-none-eabihfto Tier 2Refer to Rust's platform support page
for more information on Rust's tiered platform support.
Libraries
Location<'_>lifetime to'staticinPanic[Hook]InfoRangeInclusive::from(legacy::RangeInclusive)ManuallyDrop'sBoxinteraction has been fixedderivemacro is available at{core,std}::derive. This was previously unintentionally stabilized in 1.96, but is now explicitly accepted as a stabilized API.{core,std}::derivewill be 1.96, and not 1.98.Stabilized APIs
str::substr_range[T]::subslice_rangecore::fmt::NumBuffer<{integer}>::format_intoSend/Sync for std::process::CommandArgs{fN}::algebraic_add{fN}::algebraic_sub{fN}::algebraic_mul{fN}::algebraic_div{fN}::algebraic_remNonZero<{integer}>::from_str_radixString::from_utf16leString::from_utf16le_lossyString::from_utf16beString::from_utf16be_lossy[T]::strip_circumfixstr::strip_circumfixAtomic<T>::from_mutAtomic<T>::get_mut_sliceAtomic<T>::from_mut_slicestd::range::legacyCompatibility Notes
ambiguous_glob_importslint into a hard errorType = TypeandType == Typeare no longer syntactically allowedrepr(transparent)is now more strict about which fields have "trivial" layout and hence can be ignored:repr(C)types, types with private fields, and#[non_exhaustive]types are no longer considered "trivial"transmute()when somereprattributes are involved.derive(PartialOrd)when derivingOrdThis can break crates in practice where a type's PartialOrd and Ord impls were inconsistent with each other.
assert_eqandassert_nePartialEqimplementation, when aderive(PartialEq)implementation for that type also exists.-Zemscripten-wasm-eh=falseflag to switch back to JS exceptions has been removed.File::lockimplementation, it has the wrong semantics (return "unsupported" instead)cfg_select!This may cause more code to be formatted which was previously ignored.
v1.97.1Compare Source
==========================
This backports an LLVM submodule bump to include the LLVM-side fix and a
revert of the rustc change that is one known trigger for the bug. The rustc
side revert should not be strictly necessary but is done out of abundance of caution.
v1.97.0Compare Source
==========================
Language
Result<T, Uninhabited>andControlFlow<Uninhabited, T>to be equivalent toTfor must use lintdead_code_pub_in_binarylint for unused pub items in binary cratesdiv32,lam-bh,lamcas,ld-seq-saandscqtarget featurescfg(target_has_atomic_primitive_alignment)selfin imports in more casesPlatform Support
Refer to Rust's platform support page
for more information on Rust's tiered platform support.
Stabilized APIs
Default for RepeatNCopy for ffi::FromBytesUntilNulErrorSend for std::fs::Fileon UEFI<{integer}>::isolate_highest_one<{integer}>::isolate_lowest_one<{integer}>::highest_one<{integer}>::lowest_one<{integer}>::bit_widthNonZero<{integer}>::isolate_highest_oneNonZero<{integer}>::isolate_lowest_oneNonZero<{integer}>::highest_oneNonZero<{integer}>::lowest_oneNonZero<{integer}>::bit_widthThese previously stable APIs are now stable in const contexts:
char::is_controlCargo
build.warningsconfig. This controls how lint warnings from local packages are treated. Useful for enforcing a warning-free build in CI, replacing-Dwarnings. docsresolver.lockfile-pathconfig. This allows specifying the path to the lockfile to use when resolving dependencies. Useful when working with read-only source directories. docs--target-dirdoesn't look like a Cargo target directory. This prevents accidental deletion of non-target directories.-mshorthand for--manifest-pathcurldependency fromcrates-iocrateRustdoc
--emitflag--remap-path-prefixCompatibility Notes
f32: From<{float}>to constrain{float}pin!, in order to prevent unsoundness. The most likely case where this might impact users is: writingpin!(x)wherexhas type&mut Twill now always correctly produce a value of typePin<&mut &mut T>, instead of sometimes allowing a coercion that produces a value of typePin<&mut T>. This coercion was previously incorrectly allowed since Rust 1.88.0.std::charconstants and functionsf64methods which have been deprecated since 1.0varargs_without_patternlint in depslink_sectionspecifierenums have changed. This is not a breaking change, as it only applies toenums without layout guarantees, but is noted here as we've seen people impacted from having made assumptions about the layout algorithm.#[export_name = "..."]where the name is empty#[link_name = "..."]&#[link(name = "...")]parametersshutdownon a socket to shut down the write side, attempting to write to the socket will now produce aBrokenPipeerror rather thanOther. MapWSAESHUTDOWNtoio::ErrorKind::BrokenPipev1.96.1Compare Source
===========================
v1.96.0Compare Source
==========================
Language
exprmetavariable tocfgManuallyDropas patterns (fixing a regression introduced in 1.94.0)Compiler
riscv64gc-unknown-fuchsiabaseline to RVA22 + vectorLibraries
NonZerointegersStabilized APIs
assert_matches!debug_assert_matches!From<T> for AssertUnwindSafe<T>From<T> for LazyCell<T, F>From<T> for LazyLock<T, F>core::range::RangeToInclusivecore::range::RangeToInclusiveItercore::range::RangeFromcore::range::RangeFromItercore::range::Rangecore::range::RangeIterCargo
target.'cfg(..)'.rustdocflagssupport in configuration.Rustdoc
white-space: pre-wrap;property and stripped any<p>elements from the rendered html, however this caused issues and unintuitive behavior. The new behavior should be more predictable, however some multi-line deprecation notes will now be rendered as as single lines. If this is undesirable, you can use the standard markdown method of forcing a linebreak, which is two spaces followed by a newline ("\n").missing_doc_code_exampleslint on impl itemsCompatibility Notes
#[repr(Int)]enums in some edge cases involving fields of uninhabited zero-sized typesPin<Foo>whereFoodoesn't implementDeref. Some such coercions were previously allowed, but produce a type with no useful public API.--allow-undefinedon wasm targets#![reexport_test_harness_main]attributeuninhabited_staticlint in dependencies and make it deny-by-defaultThis appears to improve the quality of backtraces. This change has no effect on the defaults for the output of rustc/cargo on these targets.
-Csoft-float::{self [as name]}, e.g.,struct S {}; use S::{self as Other};, is now no longer permitted because{self}imports require a module parent.export_name,link_name, andlink_sectionattributes, if multiple of the same attribute is present, the first one now takes precedence.avrtargets, C'sdoubletype is 32-bit by default, so changec_doubletof32onavrtargets to match. This is a breaking change, but necessary to makec_doublematch C's double.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.
aarch64softfloat targets now have to haverustc_abiset to"softfloat"cfg(target_abi)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-defaultConfiguration
📅 Schedule: (in timezone America/New_York)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Never, 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.