chore(deps): Update compatible (dev) #5983
Merged
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:
0.1.15->0.1.210.2.6->0.2.11Release Notes
nvzqz/divan (divan)
v0.1.21Compare Source
Fixed
Divan::skip_exactbehaved incorrectly inv0.1.19.Changed
sacking the people who have just been sacked have been sacked.
v0.1.20Compare Source
Fixed
Divan::skip_regexaccidentally droppedregex_lite::Regexand behaved incorrectly in
v0.1.19.v0.1.19Compare Source
Fixed
cargo-nextest] no longer skips benchmarks with argument parameters ([#75]).Changed
v0.1.18Compare Source
Added
Support for [
cargo-nextest] running benchmarks as tests.[
prelude] module for simplifying imports of [#[bench]][bench_attr],[
#[bench_group]][bench_group_attr], [black_box], [black_box_drop],[
AllocProfiler], [Bencher], and [Divan].Support
wasiandemscriptentargets.v0.1.17Compare Source
Changed
Set [MSRV] to 1.80 for [
LazyLock] and newsize_ofprelude import.Reduced thread pool memory usage by many kilobytes by using rendezvous
channels instead of array-based channels.
v0.1.16Compare Source
Added
Thread pool for reusing threads across multi-threaded benchmarks. The result
is that when running Divan benchmarks under a sampling profiler, the
profiler's output will be cleaner and easier to understand. ([#37])
Track the maximum number of allocations during a benchmark.
Changed
Make private
Arg::gettrait method not takeself, so that text editorsdon't recommend using it. ([#59])
Cache
BenchOptionsusingLazyLockinstead ofOnceLock, saving space andsimplifying the implementation.
BurntSushi/jiff (jiff)
v0.2.11Compare Source
===================
This release includes new APIs for customizing Jiff's
strtimebehavior alongwith a few minor bug fixes. Jiff's
strtimeformatting API has also beenoptimized. It's about twice as fast as it was.
This release also coincides with the publication of
jiff-icu 0.2.0-beta.2,which has support for
icu 2.0.0-beta.2.Enhancements:
Add support for the
%c,%r,%Xand%xconversion specifiers.Add support for
%qinjiff::fmt::strtime(prints quarter of year).Add support for
%::zand%:::zinjiff::fmt::strtime.Add support for
%Ninjiff::fmt::strtime(alias for%9f).Add a "lenient" mode for
strtimeformatting APIs that ignores most errors.Bug fixes:
Document default precision behavior of
Displayimpls for datetime types.Allow whitespace in more places in RFC 2822 parser (improves spec compliance).
TimeZone::get("UTC")should now always returnTimeZone::UTC.Performance:
Jiff's
strftimeAPIs are now approximately twice as fast as they were.Performance should be comparable to
chronoandtime's prebuilt APIs.v0.2.10Compare Source
===================
This release includes a bug fix for parsing
Tuesdaywhen using%AviaJiff's
strptimeAPIs. Specifically, it would recognizeTuedayinstead ofTuesday.Bug fixes:
Fix typo in
strptimeparsing fromTuedaytoTuesday.v0.2.9Compare Source
==================
This release includes a bug fix that, in debug mode, could result in datetime
types having different hashes for the same value. This could cause problems,
for example, if you are using datetimes as keys in a hash map. This problem
didn't exist when Jiff was compiled in release mode.
This release also improves the panic message shown when the
jsfeature isn'tenabled and the current time is requested on
wasm32-unknown-unknowntargets.Enhancements:
Provide a better panic message when
Zoned::now()fails on WASM.Bug fixes:
Fix bug where
Hashon datetime types could yield different hash values forthe same underlying date/time.
v0.2.8Compare Source
==================
This release fixes a bug where the constructors on
SignedDurationfor floating point durations could panic (in debug mode) or produce
incorrect results (in release mode). This bug only impacts users of
the
try_from_secs_{f32,f64}andfrom_secs_{f32,f64}methods onSignedDuration.Enhancements:
Add an alternate
Debugimpl forSignedDurationthat only shows its secondand nanosecond components (while using only one component when the other is
zero).
Bug fixes:
Fix a bug that could produce a panic or incorrect results in
SignedDuration::(try_)?from_secs_{f32,f64}.v0.2.7Compare Source
==================
This release includes a bug fix that changes how an empty but set
TZenvironment variable is interpreted (as indistinguishable from
TZ=UTC).This also includes a new enabled by default create feature,
perf-inline,which allows toggling Jiff's use of
inline(always). This may help improvecompile times or decrease binary size.
Enhancements:
Remove some internal uses of generics to mildly improve compile times.
Add
perf-inlinecrate feature for controllinginline(always)annotations.Bug fixes:
Make
TZ=indistinguishable fromTZ=UTC.Configuration
📅 Schedule: Branch creation - "before 5am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.