rust/library/std/src/io/error.rs, branch 1.71.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.71.02023-04-12T17:27:18+00:00remove some unneeded imports2023-04-12T17:27:18+00:00KaDiWakalle.wachsmuth@gmail.com2022-08-09T00:14:43+00:00urn:sha1:ad2b34d0e37e2f968f226e2401bcb894207ca1c5Rollup merge of #106964 - workingjubilee:crouching-ioerror-hidden-documentation, r=ChrisDenton2023-03-23T18:55:42+00:00Matthias Krügermatthias.krueger@famsik.de2023-03-23T18:55:42+00:00urn:sha1:aeabe34d79a61f772e64e5fba3f1f09d4a9c9e5e
Clarify `Error::last_os_error` can be weird
Fundamentally, querying the OS for error codes is a process that is deeply subject to the whims of chance and fortune. We can account for OS, but not for every combination of platform APIs. A compiled binary may not recognize new errors introduced years later. We should clarify a few especially odd situations, and what they mean: We can effectively promise nothing... if you ask for Rust to decode errors where none have occurred.
This allows removing mention of ErrorKind::Uncategorized.
That error variant is hidden deliberately, so we should not explicitly mention it.
This fixes #106937.
Since you had an opinion also: Does this solution seem acceptable?
r? ``@ChrisDenton``
Remove irrelevant docs on error kinds2023-03-17T21:26:02+00:00Jubilee Youngworkingjubilee@gmail.com2023-03-17T21:24:11+00:00urn:sha1:0f32fd8484d3282648dc18985b7d29abad2d6b70std: add tracking issue for `RawOsError`2023-02-08T11:35:27+00:00joboetjonasboettiger@icloud.com2023-02-08T11:35:27+00:00urn:sha1:6a5331146cc77b47ba431a3acf546bda15c9057cstd: add type alias for raw OS errors2023-01-31T16:23:35+00:00joboetjonasboettiger@icloud.com2023-01-31T16:20:37+00:00urn:sha1:42cc28ac8b7de426b4ae615242acd0be1bfa9a58
Implement rust-lang/libs-team#173.
Explain the "no-error" io::Error case2023-01-17T04:58:15+00:00Jubilee Youngworkingjubilee@gmail.com2023-01-17T03:27:18+00:00urn:sha1:2d927cc1941cce6f320640836941ca480e958ead
Fundamentally, querying the OS for error codes is a process
that is deeply subject to the whims of chance and fortune.
We can account for OS, but not for every combination of platform APIs.
A compiled binary may not recognize new errors introduced years later.
We should clarify a few especially odd situations, and what they mean:
We can effectively promise nothing.
This allows removing mention of ErrorKind::Uncategorized.
That error variant is hidden quite deliberately, so we
should not explicitly mention it.
Rollup merge of #103067 - Nilstrieb:tidy-likes-the-alphabet, r=jackh7262022-10-14T21:43:46+00:00Matthias Krügermatthias.krueger@famsik.de2022-10-14T21:43:46+00:00urn:sha1:a96f1a8a1eef38f024d6fcff932f55a2a760a395
More alphabetical sorting
Sort and enforce a few more things. The biggest change here is sorting all target features.
Add some tidy-alphabetical2022-10-14T19:18:03+00:00nils48135649+Nilstrieb@users.noreply.github.com2022-10-14T19:18:03+00:00urn:sha1:3c0062641d02940a66bc74b182aa924d141060c1Tweak grammar2022-10-14T11:17:07+00:00Josh Triplettjosh@joshtriplett.org2022-10-14T11:17:07+00:00urn:sha1:f95e8532222479c417fdf9fffc6ce1ab8cda3413Improved documentation for `std::io::Error`2022-10-07T12:42:05+00:00StackOverflowExcept1on109800286+StackOverflowExcept1on@users.noreply.github.com2022-10-07T12:42:05+00:00urn:sha1:4cf30c0022a434718799b66cdf8911ad8030d0e1