about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp
diff options
context:
space:
mode:
authorMara Bos <m-ou.se@m-ou.se>2021-08-16 23:37:28 +0200
committerGitHub <noreply@github.com>2021-08-16 23:37:28 +0200
commitbeeff0440ff977228be9ea4f38b76daaccfbe4ea (patch)
treee3fc8ad0880f9bc929e3d3ab13f3cc905a552e79 /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp
parentd7df1b13da463011a843383a20c0fd4f111d3564 (diff)
parent079bf755a3449a61e61714a17d00f21337f2471e (diff)
downloadrust-beeff0440ff977228be9ea4f38b76daaccfbe4ea.tar.gz
rust-beeff0440ff977228be9ea4f38b76daaccfbe4ea.zip
Rollup merge of #87967 - m-ou-se:non-fmt-panic-detect-fake-spans, r=cjgillot
Detect fake spans in non_fmt_panic lint.

This addresses https://github.com/rust-lang/rust/issues/87621

Some proc_macros claim that the user wrote all of the tokens it outputs, by applying a span from the input to all of the produced tokens. That can result in confusing suggestions, as in #87621. This is a simple patch that avoids suggesting anything for `panic!("{}")` if the span of `"{}"` and `panic!(..)` are identical, which is normally not possible.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions