SmolStrBuilder: move rather than alloc + copy on finish #21194
+4
−4
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.
Removing unnessecary len checks as well as 1 redundant alloc + copy on finishing a Builder into a SmolStr.
Browsing the old repo for smolstr i came about an issue that mentioned a redundant alloc + copy when finishing a SmolStrBuilder (rust-analyzer/smol_str#94) by @alexheretic.
The solution passes all tests and skips the conditional tests in the Repr::new(), and as long as the internal String has not too much unused capacity the will skip a reallocation + copy. (into_boxed_str() uses shrink_to_fit)
NOTE: It does change the finish function signature. finish() took a &self so far. This is contrary to what a user would understand from the word finish, imo.
Someone with merging power needs to decide if this change of signature is acceptable.