perf: avoid using write! macro with single str#228
Merged
epage merged 1 commit intorust-cli:mainfrom Nov 1, 2024
Merged
Conversation
034dd12 to
4c4eaf9
Compare
strstr
4c4eaf9 to
fb843c5
Compare
Pull Request Test Coverage Report for Build 11629840392Details
💛 - Coveralls |
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
3 participants
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.
A known issue with
write!is that it's slower and generates more code than direct calls towrite_str, unfortunately even in the simple case of"{str}". See rust-lang/rust#76490.I've verified with Godbolt that it is still the case: https://godbolt.org/z/sq3M8xWfo