tmp/tmp_m92h_qx/{from.md → to.md}
RENAMED
|
@@ -1,9 +1,14 @@
|
|
| 1 |
#### Enum `path::format` <a id="fs.enum.path.format">[[fs.enum.path.format]]</a>
|
| 2 |
|
| 3 |
This enum specifies constants used to identify the format of the
|
| 4 |
character sequence, with the meanings listed in [[fs.enum.path.format]].
|
| 5 |
|
| 6 |
-
|
| 7 |
-
|
| 8 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 9 |
|
|
|
|
| 1 |
#### Enum `path::format` <a id="fs.enum.path.format">[[fs.enum.path.format]]</a>
|
| 2 |
|
| 3 |
This enum specifies constants used to identify the format of the
|
| 4 |
character sequence, with the meanings listed in [[fs.enum.path.format]].
|
| 5 |
|
| 6 |
+
**Table: Enum `path::format`** <a id="fs.enum.path.format">[fs.enum.path.format]</a>
|
| 7 |
+
|
| 8 |
+
| Name | Meaning |
|
| 9 |
+
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
| 10 |
+
| `native_format` | The native pathname format. |
|
| 11 |
+
| `generic_format` | The generic pathname format. |
|
| 12 |
+
| `auto_format` | The interpretation of the format of the character sequence is implementation-defined. The implementation may inspect the content of the character sequence to determine the format. Recommended practice: For POSIX-based systems, native and generic formats are equivalent and the character sequence should always be interpreted in the same way. |
|
| 13 |
+
|
| 14 |
|