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.0.51
->2.0.0
Release Notes
dtolnay/thiserror (thiserror)
v2.0.0
Compare Source
Breaking changes
Referencing keyword-named fields by a raw identifier like
{r#type}
inside a format string is no longer accepted; simply use the unraw name like{type}
(#347)This aligns thiserror with the standard library's formatting macros, which gained support for implicit argument capture later than the release of this feature in thiserror 1.x.
Trait bounds are no longer inferred on fields whose value is shadowed by an explicit named argument in a format message (#345)
Tuple structs and tuple variants can no longer use numerical
{0}
{1}
access at the same time as supplying extra positional arguments for a format message, as this makes it ambiguous whether the number refers to a tuple field vs a different positional arg (#354)Code containing invocations of thiserror's
derive(Error)
must now have a direct dependency on thethiserror
crate regardless of the error data structure's contents (#368, #369, #370, #372)Features
Support disabling thiserror's standard library dependency by disabling the default "std" Cargo feature:
thiserror = { version = "2", default-features = false }
(#373)Support using
r#source
as field name to opt out of a field named "source" being treated as an error'sError::source()
(#350)Infinite recursion in a generated Display impl now produces an
unconditional_recursion
warning (#359)A new attribute
#[error(fmt = path::to::myfmt)]
can be used to write formatting logic for an enum variant out-of-line (#367)Enums with an enum-level format message are now able to have individual variants that are
transparent
to supersede the enum-level message (#366)v1.0.68
Compare Source
v1.0.67
Compare Source
v1.0.66
Compare Source
v1.0.65
Compare Source
v1.0.64
Compare Source
v1.0.63
Compare Source
v1.0.62
Compare Source
#[error("…", …)]
attribute (#309)v1.0.61
Compare Source
core::fmt
andcore::panic
to facilitateerror_in_core
support (#299, thanks @jordens)v1.0.60
Compare Source
v1.0.59
Compare Source
debug-fmt-detail
option (#297)v1.0.58
Compare Source
v1.0.57
Compare Source
Display
impl for error message which do not contain any interpolated value (#286, thanks @nyurik)v1.0.56
Compare Source
v1.0.55
Compare Source
v1.0.54
Compare Source
v1.0.53
Compare Source
v1.0.52
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.