diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2023-05-04 19:18:21 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-05-04 19:18:21 +0200 |
| commit | ea0b6504faa95dd4bfb0666cbcb5dfcfe0591313 (patch) | |
| tree | fa4ad464202284442a0b227f262f6a048b006040 /tests/rustdoc-js-std/parser-errors.js | |
| parent | 8d66f01ab50870c63f85c3c7395347e5b82caa88 (diff) | |
| parent | 8c781b0906209e81f3540d1495becddae9894a25 (diff) | |
| download | rust-ea0b6504faa95dd4bfb0666cbcb5dfcfe0591313.tar.gz | |
Rollup merge of #111009 - scottmcm:ascii-char, r=BurntSushi
Add `ascii::Char` (ACP#179)
ACP second: https://github.com/rust-lang/libs-team/issues/179#issuecomment-1527900570
New tracking issue: https://github.com/rust-lang/rust/issues/110998
For now this is an `enum` as `@kupiakos` [suggested](https://github.com/rust-lang/libs-team/issues/179#issuecomment-1527959724), with the variants under a different feature flag.
There's lots more things that could be added here, and place for further doc updates, but this seems like a plausible starting point PR.
I've gone through and put an `as_ascii` next to every `is_ascii`: on `u8`, `char`, `[u8]`, and `str`.
As a demonstration, made a commit updating some formatting code to use this: https://github.com/scottmcm/rust/commit/ascii-char-in-fmt (I don't want to include that in this PR, though, because that brings in perf questions that don't exist if this is just adding new unstable APIs.)
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions