fmt: Skip calling write_str for empty strings #31966
Closed
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
`format_args!` uses one string literal per used `{}`, in many cases, the
separating string pieces are empty.
For example, `write!(w, "{}", x);` will attempt to write one empty
string before the `{}` format, and `write!(w, "{}{}{}", x, y, z);" will
write three empty string pieces between formats.
Simply skip writing if the string is empty. It is a cheap branch
compared to the virtual Write::write_str call that it makes possible to
skip.
It does not solve issue rust-lang#10761 in any way, yet that's where I noticed
this. The testcase in the issue shows a performance difference between
`write!(w, "abc")` and `write!(w, "{}", "abc")`, and this change halves
the size of the difference.
|
(rust_highfive has picked a reviewer for you, use r? to override) |
|
I wonder if it may make sense to optimize away these at compile time instead of runtime? They're taking up space in rodata and it may make sense to get rid of them? That may be a bit difficult, however, as we'd have to describe what piece is used when |
|
Yes, that's even better. I don't know how all the pieces work, but maybe there's a way to do it. |
|
☔ The latest upstream changes (presumably #32390) made this pull request unmergeable. Please resolve the merge conflicts. |
|
Closing for now. Benchmarks on this weren't that radical anyway (less than 10% savings or so). |
tbu-
added a commit
to tbu-/rust
that referenced
this pull request
Mar 21, 2017
This means that `writeln!(something, "{}{}", s1, s2)` no longer calls
`write_str` two times with empty strings (before each substitution).
See rust-lang#31966 for an earlier attempt.
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.
fmt: Skip calling write_str for empty strings
format_args!uses one string literal per used{}, in many cases, theseparating string pieces are empty.
For example,
write!(w, "{}", x);will attempt to write one emptystring before the
{}format, andwrite!(w, "{}{}{}", x, y, z);"willwrite one empty string piece between each format.
Simply skip writing if the string is empty. It is a cheap branch
compared to the virtual Write::write_str call that it makes possible to
skip.
It does not solve issue #10761 in any way, yet that's where I noticed
this. The testcase in the issue shows a performance difference between
write!(w, "abc")andwrite!(w, "{}", "abc"), and this change halvesthe size of the difference.