diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2023-02-26 12:04:57 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-02-26 12:04:57 +0100 |
| commit | 2bc553c6ea6243ecaee79ebe7a6fb5c6595e5eb9 (patch) | |
| tree | 02680f3a814060640fed46849a35917be79f9022 /compiler/rustc_errors/src | |
| parent | 70fd012439d75fd6ce561a6518b9b8fd399f455f (diff) | |
| parent | 53fb43365258bee55d796ba360835a9d6fcef9a5 (diff) | |
| download | rust-2bc553c6ea6243ecaee79ebe7a6fb5c6595e5eb9.tar.gz rust-2bc553c6ea6243ecaee79ebe7a6fb5c6595e5eb9.zip | |
Rollup merge of #107941 - compiler-errors:str-has-u8-slice-for-auto, r=lcnr
Treat `str` as containing `[u8]` for auto trait purposes Wanted to gauge ``@rust-lang/lang`` and ``@rust-lang/types`` teams' thoughts on treating `str` as "containing" a `[u8]` slice for auto-trait purposes. ``@dtolnay`` brought this up in https://github.com/rust-lang/rust/issues/13231#issuecomment-1399386472 as a blocker for future `str` type librarification, and I think it's both a valid concern and very easy to fix. I'm interested in actually doing that `str` type librarification (#107939), but this probably should be considered in the mean time regardless of that PR. r? types for the impl, though this definitely needs an FCP.
Diffstat (limited to 'compiler/rustc_errors/src')
0 files changed, 0 insertions, 0 deletions