diff options
| author | bors <bors@rust-lang.org> | 2020-10-08 21:33:32 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2020-10-08 21:33:32 +0000 |
| commit | 265e4841b7d8ee26ed0d642075f3c90496ba610a (patch) | |
| tree | 2be47e6314e0a4cfff0957994e1f2179e318d4dc /compiler/rustc_codegen_llvm/src | |
| parent | 6bfc19c687f30f05e33028a22bd321204c53bf43 (diff) | |
| parent | c81bea45f480d9d5a785778c944a3ad3daf30d27 (diff) | |
| download | rust-265e4841b7d8ee26ed0d642075f3c90496ba610a.tar.gz rust-265e4841b7d8ee26ed0d642075f3c90496ba610a.zip | |
Auto merge of #6117 - dtolnay:string_lit_as_bytes, r=ebroto
Downgrade string_lit_as_bytes to nursery Between #1402 (regarding `to_owned`) and #4494 (regarding `impl Read`), as well as other confusion I've seen hit in my work codebase involving string_lit_as_bytes (`"...".as_bytes().into()`), I don't think this lint is at a quality to be enabled by default. I would consider re-enabling this lint after it is updated to understand when the surrounding type information is sufficient to unsize `b"..."` to &\[u8\] without causing a type error. As currently implemented, this lint is pushing people to write `&b"_"[..]` which is not an improvement over `"_".as_bytes()` as far as I am concerned. --- changelog: Remove string_lit_as_bytes from default set of enabled lints
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions