Working with Paths
The difference between
PathBuf is roughly the same as the one between
Path only holds a reference to the path string data but doesn’t own this data,
PathBuf owns the string data itself. This means that a
Path is immutable and can’t be used
longer than the actual data (held somewhere else) is available.
The reason why both types exists is to avoid allocations where possible. As most functions take both
PathBuf as arguments (by using
AsRef<Path> for example), this usually doesn’t have a big
impact on your code.
A very rough guide for when to use
For return types:
If your function gets passed a
Path[Buf]and returns a subpath of it, you can just return a
If you create a new path, or combine paths or anything like that, you need to return a
PathBufif you need to store it somewhere.
In public interfaces, you usually don’t want to use
PathBufdirectly, but rather a generic
P: Into<PathBuf>. That way the caller can pass in