diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2023-03-23 19:55:42 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-03-23 19:55:42 +0100 |
| commit | aeabe34d79a61f772e64e5fba3f1f09d4a9c9e5e (patch) | |
| tree | 59c68d4dbe172c49a771a11e3b9002584dceef5d /compiler/rustc_codegen_llvm/src/errors.rs | |
| parent | df7fd9995f10627f25ccb325f693a11b3395a73c (diff) | |
| parent | 0f32fd8484d3282648dc18985b7d29abad2d6b70 (diff) | |
| download | rust-aeabe34d79a61f772e64e5fba3f1f09d4a9c9e5e.tar.gz rust-aeabe34d79a61f772e64e5fba3f1f09d4a9c9e5e.zip | |
Rollup merge of #106964 - workingjubilee:crouching-ioerror-hidden-documentation, r=ChrisDenton
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``
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions