about summary refs log tree commit diff
path: root/compiler/rustc_pattern_analysis/src
diff options
context:
space:
mode:
authorStuart Cook <Zalathar@users.noreply.github.com>2025-05-09 16:25:03 +1000
committerGitHub <noreply@github.com>2025-05-09 16:25:03 +1000
commitb165a4c2809a610a52bcbaae28cd4989ff684a1e (patch)
treea9d4ab8427208bc9ccc05022fefcec7e3da380b6 /compiler/rustc_pattern_analysis/src
parentc8b7f32434c0306db5c1b974ee43443746098a92 (diff)
parent88c1796384cca81ca80e728d45f6673f601493ff (diff)
downloadrust-b165a4c2809a610a52bcbaae28cd4989ff684a1e.tar.gz
rust-b165a4c2809a610a52bcbaae28cd4989ff684a1e.zip
Rollup merge of #140801 - xizheyin:issue-140747, r=SparrowLii
Use span before macro expansion in lint for-loops-over-falibles

Fixes #140747

I think there are going to be a lot of cases where macros are expanded in the compiler resulting in span offsets, and I'd like to know how that's typically handled. Does it have to be handled specially every time?
Diffstat (limited to 'compiler/rustc_pattern_analysis/src')
0 files changed, 0 insertions, 0 deletions