| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2024-01-11 | std: begin moving platform support modules into `pal` | joboet | -17/+0 | |
| 2023-09-01 | fix(std): Rename os_str_bytes to encoded_bytes | Ed Page | -2/+2 | |
| 2023-03-27 | Allow access to `OsStr` bytes | Ed Page | -5/+4 | |
| `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 #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). | ||||
| 2022-08-20 | Expose `Utf8Lossy` as `Utf8Chunks` | dylni | -0/+8 | |
| 2022-03-10 | Use implicit capture syntax in format_args | T-O-R-U-S | -1/+1 | |
| This updates the standard library's documentation to use the new syntax. The documentation is worthwhile to update as it should be more idiomatic (particularly for features like this, which are nice for users to get acquainted with). The general codebase is likely more hassle than benefit to update: it'll hurt git blame, and generally updates can be done by folks updating the code if (and when) that makes things more readable with the new format. A few places in the compiler and library code are updated (mostly just due to already having been done when this commit was first authored). | ||||
| 2021-07-03 | Move `os_str_bytes` to `sys::unix` and reuse it on other platforms. | Christiaan Dirkx | -0/+10 | |
