diff options
| author | bors <bors@rust-lang.org> | 2024-02-27 18:19:43 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-02-27 18:19:43 +0000 |
| commit | 0ac05c05271f31c43d31017cbd288e8737a0edb0 (patch) | |
| tree | ff67bdc97009b2222764b4c92c5b063f2430274e /compiler/rustc_codegen_llvm/src | |
| parent | a41cec9f7c6dbbabdc9134879a640ceadd3a516d (diff) | |
| parent | 000579477067d43787617c5e44cc02a7246e5cc8 (diff) | |
| download | rust-0ac05c05271f31c43d31017cbd288e8737a0edb0.tar.gz rust-0ac05c05271f31c43d31017cbd288e8737a0edb0.zip | |
Auto merge of #16697 - regexident:relpath-to-relpathbuf, r=Veykril
Add `to_path_buf()` method for `RelPath`
There seems to be no ergonomic way to obtain a `RelPathBuf` from a corresponding `&RelPath` at the moment, making the latter sort of a dead end.
The `AbsPath` type provides the following:
```rust
impl AbsPath {
// ...
/// Equivalent of [`Path::to_path_buf`] for `AbsPath`.
pub fn to_path_buf(&self) -> AbsPathBuf {
AbsPathBuf::try_from(self.0.to_path_buf()).unwrap()
}
// ...
}
```
So I took the liberty of adding a corresponding equivalent for `RelPath:
```rust
impl RelPath {
// ...
/// Equivalent of [`Path::to_path_buf`] for `RelPath`.
pub fn to_path_buf(&self) -> RelPathBuf {
RelPathBuf::try_from(self.0.to_path_buf()).unwrap()
}
// ...
}
```
(the change is motivated by an outside use of the `ra_ap_paths` crate that would benefit from being able to use `RelPath` and `AbsPath` over `Path`)
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions
