diff options
| author | Dylan DPC <99973273+Dylan-DPC@users.noreply.github.com> | 2022-09-21 19:01:09 +0530 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-09-21 19:01:09 +0530 |
| commit | 77d063b9544e9f438c56474efea4e07ab0d0e1e4 (patch) | |
| tree | ae73a215c4aa8f03d143654de711369a9429143b /library/std/src/sys/unix/process/process_unix.rs | |
| parent | 7d7f55599ac2c4d433d4390339ea9a52489dbe0e (diff) | |
| parent | c291d2adecbf13685ed321d7699ba7bb0b60806a (diff) | |
| download | rust-77d063b9544e9f438c56474efea4e07ab0d0e1e4.tar.gz rust-77d063b9544e9f438c56474efea4e07ab0d0e1e4.zip | |
Rollup merge of #102058 - mqudsi:path_extension_docs, r=thomcc
Clarify Path::extension() semantics in docs abstract State up-front and center what shape the returned extension will have, without making the user read through the description and examples. This is a doc-only change. There are no changes to the API contract and the clarification is in line with what was already stated/promised in the existing doc text - just clarified, summarized, and served bright and early. Rationale: Various frameworks and libraries for different platforms have their different conventions as to whether an "extension" is ".ext" or just "ext" and anyone that's had to deal with this ambiguity in the past is always double- or triple-checking to make sure the function call returns an extension that matches the expected semantics. Offer the answer to this important question right off the bat instead of making them dig to find it. ```@rustbot``` label +A-docs
Diffstat (limited to 'library/std/src/sys/unix/process/process_unix.rs')
0 files changed, 0 insertions, 0 deletions