fix: correct SerializeField definition #3040
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.
Motivation
Clippy in 1.80.0 alerted us to the fact that
SerializeField
was neverconstructed (and due to its non-
pub
member, it can't be constructedoutside the
tracing-serde
crate where it's from).Solution
This change fixes the definition to hold a reference to a
Field
, whichis what the other
Serialize*
types do. It also implementsAsSerde
for this type and uses it inside the
SerializeFieldSet
type.As a bonus, Clippy is now also happy that the type is constructed.
The example collector in the
tracing-serde
crate was also renamed fromJsonSubscriber
toJsonCollector
.