Repository navigation
perf: reduce renderer timestamp allocations - #217
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reduces transient timestamp strings in the default UTC, JSON and ext-json renderers while preserving the existing RFC3339 bytes, fractional precision and timezone suffixes. Adds regressions covering fractional seconds, leap seconds, dates outside the usual year range and timestamp zones.
Validation: cargo fmt --all --check, cargo audit, cargo build --workspace --locked, and 16 renderer tests passed. Independent review found no actionable issues. Audit retains the existing allowed proc-macro-error2 unmaintained warning. Allocation improvements are based on the changed allocation paths; no throughput speedup is claimed.
DSK-141