Avoid using owned String for package name constructors
#11768
Merged
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.
Summary
Since we use
SmallStringinternally, there's no benefit to passing an owned string to thePackageNameconstructor (same goes forExtraName, etc.). I've kept them for now (maybe that will change in the future, so it's useful to have clients passed own values if they can), but removed a bunch of usages where we were casting from&strtoStringneedlessly to use the constructor.