diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2022-02-15 16:02:35 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-02-15 16:02:35 +0100 |
| commit | c6b27db8767a6e070701d22a179caac60592f713 (patch) | |
| tree | f3920481c5835837d0061d7eb573a8956e7cf759 /compiler/rustc_codegen_llvm/src/llvm/mod.rs | |
| parent | e1baa3d5b959ae6c74b6e83292a5db33d4ebf7db (diff) | |
| parent | e59cda9ee1b9fab3fe966ea7e4b12c14b1f85789 (diff) | |
| download | rust-c6b27db8767a6e070701d22a179caac60592f713.tar.gz rust-c6b27db8767a6e070701d22a179caac60592f713.zip | |
Rollup merge of #93999 - barzamin:suggest-raw-strings, r=jackh726
suggest using raw strings when invalid escapes appear in literals i'd guess about 70% of "bad escape" cases occur when someone meant to use a raw string literal because they're passing it directly to `Regex::new()`. this emits an advisory (`Applicability::MaybeIncorrect`) `help:` suggestion to the user that they use an `r""` string, on top of the normal notes about looking at the string literal documentation/spec.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/llvm/mod.rs')
0 files changed, 0 insertions, 0 deletions