Dylan DPC 9f6a2fde34 Rollup merge of #99335 - Dav1dde:fromstr-docs, r=JohnTitor ... Use split_once in FromStr docs Current implementation: ```rust fn from_str(s: &str) -> Result<Self, Self::Err> { let coords: Vec<&str> = s.trim_matches(|p| p == '(' || p == ')' ) .split(',') .collect(); let x_fromstr = coords[0].parse::<i32>()?; let y_fromstr = coords[1].parse::<i32>()?; Ok(Point { x: x_fromstr, y: y_fromstr }) } ``` Creating the vector is not necessary, `split_once` does the job better. Alternatively we could also remove `trim_matches` with `strip_prefix` and `strip_suffix`: ```rust let (x, y) = s .strip_prefix('(') .and_then(|s| s.strip_suffix(')')) .and_then(|s| s.split_once(',')) .unwrap(); ``` The question is how much 'correctness' is too much and distracts from the example. In a real implementation you would also not unwrap (or originally access the vector without bounds checks), but implementing a custom Error and adding a `From<ParseIntError>` and implementing the `Error` trait adds a lot of code to the example which is not relevant to the `FromStr` trait.		2022-07-19 11:38:53 +05:30
..
benches	Add unicode fast path to is_printable	2022-05-31 10:51:35 +02:00
primitive_docs	Add primitive documentation to libcore	2021-09-12 02:23:08 +00:00
src	Rollup merge of #99335 - Dav1dde:fromstr-docs, r=JohnTitor	2022-07-19 11:38:53 +05:30
tests	Rollup merge of #98839 - 5225225:assert_transmute_copy_size, r=thomcc	2022-07-18 21:14:42 +05:30
Cargo.toml	Avoid use of rand::thread_rng in stdlib benchmarks	2022-05-02 00:08:21 -07:00