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.
Introducing optional span tracking (line, column, byte offset).
The feature is behind a new feature flag called
spanned
. It introducesSpanned<T>
, with wich you can get serde_json (when calling the appropriate deserializer) to inject span information into customDeserialize
types.SpannedValue
a copy ofValue
that usesSpanned<T>
to provide span information.This PR still needs a bit of fixing up:
Read::position
as itscolumn
isn't what we want and itsline
is slow to computeAnd then a good chunk of polishing:
SpannedValue
functionality is 90% copy-pasta fromValue
)However, before I proceed with any of that, and since I've already put a good amount hours into this, I'd first like to get initial feedback on/review of the general design (API, outlined provided functionality).
Here's the gist of how it'd work
Sample code with output
Produces
Closes: #637