Rollup merge of #37372 - vtduncan:pathbuf-docs-link, r=steveklabnik
Link to PathBuf from the Path docs I got stuck trying to use `Path` when `PathBuf` was what I needed. Hopefully this makes `PathBuf` and the module docs a bit easier to find for others. r? @steveklabnik
This commit is contained in:
commit
e948cf17bc
1 changed files with 7 additions and 3 deletions
|
|
@ -1294,14 +1294,18 @@ impl Into<OsString> for PathBuf {
|
|||
/// This type supports a number of operations for inspecting a path, including
|
||||
/// breaking the path into its components (separated by `/` or `\`, depending on
|
||||
/// the platform), extracting the file name, determining whether the path is
|
||||
/// absolute, and so on. More details about the overall approach can be found in
|
||||
/// the module documentation.
|
||||
/// absolute, and so on.
|
||||
///
|
||||
/// This is an *unsized* type, meaning that it must always be used behind a
|
||||
/// pointer like `&` or [`Box`].
|
||||
/// pointer like `&` or [`Box`]. For an owned version of this type,
|
||||
/// see [`PathBuf`].
|
||||
///
|
||||
/// [`str`]: ../primitive.str.html
|
||||
/// [`Box`]: ../boxed/struct.Box.html
|
||||
/// [`PathBuf`]: struct.PathBuf.html
|
||||
///
|
||||
/// More details about the overall approach can be found in
|
||||
/// the module documentation.
|
||||
///
|
||||
/// # Examples
|
||||
///
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue