Replace PathBuf/Utf8PathBuf with Path/Utf8Path when ownership not needed #4440
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.
Using
&Path/&Utf8Path
as function parameter type provides better generality over&PathBuf/&Utf8PathBuf
, as it can accept both&Path/&Utf8Path
and&PathBuf/&Utf8PathBuf
.When it comes to constructor,
Path::new()
doesn't introduce overhead of heap allocation, whilePathBuf::from()
does.Public API changes documented in changelogs (optional)