Make DelayedFormat
hold a generic offset
#1559
Open
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.
Just learned that adding a type parameter is a backwards-compatible change if it has a default type, thanks to RFC 0213.
That means we can fix the biggest remaining performance problem with
DelayedFormat
, and make our formatting work without allocations! 🎉In this PR I only added an extra generic parameter to
DelayedFormat
. Making our formatting work without allocating needs one more tricky thing that is best for another PR.To quote from #1163:
By taking the offset as a generic we can delay formatting the timezone name until it is needed, which often is never.
To keep the deprecated
format::{format, format_items}
functions working (which expect aString
andFixedOffset
instead of a generic offset) I had to add anOffsetWrapper
type.Benchmarks