Update edition to 2021 & specify optional dependency pathway unambiguously #35
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.
Couple of small "maintenance" things:
dep:crate
syntax to specify the dependency onserde
by theserde_impl
featurepub
visibilities#[inline]
attributes onserialize
andvisit_seq
in the ser/de implementations. These can already be inlined even without LTO cross-crate because they are generic. There is also little reason to explicitly hint these to encourage additional inlining without a reason grounded in data due to their nature.