Mahmoud Al-Qudsi c291d2adec 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. 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.		2022-09-20 11:12:03 -05:00
..
benches	mv std libs to library/	2020-07-27 19:51:13 -05:00
primitive_docs	Add primitive documentation to libcore	2021-09-12 02:23:08 +00:00
src	Clarify Path::extension() semantics in docs abstract	2022-09-20 11:12:03 -05:00
tests	Fold aarch64 feature +fp into +neon	2022-03-22 15:14:33 -07:00
build.rs	Library changes for Apple WatchOS	2022-07-20 08:57:36 +01:00
Cargo.toml	Update stdarch	2022-09-15 13:05:28 -04:00