diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-09-06 07:33:57 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-09-06 07:33:57 +0200 |
| commit | 45d6957f241ee48fe1a149a91d9c9f7f6d7aae4f (patch) | |
| tree | 6a7c5a84e465e1ceebafac5d0365600fe3cdb49b /compiler/rustc_codegen_llvm/src/llvm/diagnostic.rs | |
| parent | b09f3160582c7a2d5e07bc37999925df721bbbbb (diff) | |
| parent | 49a93df77d3c617e14fd466f30d06b4ab54a64df (diff) | |
| download | rust-45d6957f241ee48fe1a149a91d9c9f7f6d7aae4f.tar.gz rust-45d6957f241ee48fe1a149a91d9c9f7f6d7aae4f.zip | |
Rollup merge of #129963 - rjooske:fix/inaccurate_to_string_lossy_doc, r=workingjubilee
Inaccurate `{Path,OsStr}::to_string_lossy()` documentation
The documentation of `Path::to_string_lossy()` and `OsStr::to_string_lossy()` says the following:
> Any non-Unicode sequences are replaced with `U+FFFD REPLACEMENT CHARACTER`
which didn't immediately make sense to me. ("non-Unicode sequences"?)
Since both `to_string_lossy` functions eventually become just a call to `String::from_utf8_lossy`, I believe the documentation meant to say:
> Any *non-UTF-8* sequences are replaced with `U+FFFD REPLACEMENT CHARACTER`
This PR corrects this mistake in the documentation.
For the record, a similar quote can be found in the documentation of `String::from_utf8_lossy`:
> ... During this conversion, `from_utf8_lossy()` will replace any invalid UTF-8 sequences with `U+FFFD REPLACEMENT CHARACTER`, ...
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/llvm/diagnostic.rs')
0 files changed, 0 insertions, 0 deletions