diff options
| author | bors <bors@rust-lang.org> | 2023-05-30 21:26:22 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-05-30 21:26:22 +0000 |
| commit | 9610dfe5a9a731ced1ea4923ecbd0c57fe367898 (patch) | |
| tree | 9d34e6dd7c85cc272964c3b8232e401cea3bbfea /compiler/rustc_errors/src/snippet.rs | |
| parent | f0411ffcebcd7f75ac02ed45feb53ffd07b75398 (diff) | |
| parent | e6a35c49533dd734f178b04677404df0da518737 (diff) | |
| download | rust-9610dfe5a9a731ced1ea4923ecbd0c57fe367898.tar.gz rust-9610dfe5a9a731ced1ea4923ecbd0c57fe367898.zip | |
Auto merge of #109698 - epage:wtf, r=Amanieu
Allow limited access to `OsStr` bytes `OsStr` has historically kept its implementation details private out of concern for locking us into a specific encoding on Windows. This is an alternative to rust-lang#95290 which proposed specifying the encoding on Windows. Instead, this only specifies that for cross-platform code, `OsStr`'s encoding is a superset of UTF-8 and defines rules for safely interacting with it At minimum, this can greatly simplify the `os_str_bytes` crate and every arg parser that interacts with `OsStr` directly (which is most of those that support invalid UTF-8). Tracking issue: #111544
Diffstat (limited to 'compiler/rustc_errors/src/snippet.rs')
0 files changed, 0 insertions, 0 deletions
