mirror of
https://github.com/rust-lang/rust.git
synced 2024-10-31 22:41:50 +00:00
2bc553c6ea
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. |
||
---|---|---|
.. | ||
auto-is-contextual.rs | ||
auto-trait-projection-recursion.rs | ||
auto-trait-validation.fixed | ||
auto-trait-validation.rs | ||
auto-trait-validation.stderr | ||
auto-traits.rs | ||
bad-generics-on-dyn.rs | ||
bad-generics-on-dyn.stderr | ||
issue-23080-2.rs | ||
issue-23080-2.stderr | ||
issue-23080.rs | ||
issue-23080.stderr | ||
issue-84075.rs | ||
issue-84075.stderr | ||
str-contains-slice-conceptually.rs | ||
str-contains-slice-conceptually.stderr | ||
suspicious-impls-lint.rs | ||
suspicious-impls-lint.stderr | ||
typeck-auto-trait-no-supertraits-2.rs | ||
typeck-auto-trait-no-supertraits-2.stderr | ||
typeck-auto-trait-no-supertraits.rs | ||
typeck-auto-trait-no-supertraits.stderr | ||
typeck-default-trait-impl-constituent-types-2.rs | ||
typeck-default-trait-impl-constituent-types-2.stderr | ||
typeck-default-trait-impl-constituent-types.rs | ||
typeck-default-trait-impl-constituent-types.stderr | ||
typeck-default-trait-impl-negation.rs | ||
typeck-default-trait-impl-negation.stderr | ||
typeck-default-trait-impl-precedence.rs | ||
typeck-default-trait-impl-precedence.stderr |