about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2022-03-30 16:57:24 +0000
committerbors <bors@rust-lang.org>2022-03-30 16:57:24 +0000
commitfe7254ff6f9ed485fe3d8b31c97c0beac1102d12 (patch)
treeecea6b02274553d0458bc098b13cd62f23a6efeb /compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp
parentdf7c253d398a5c469b656924fbd51748f1814183 (diff)
parentaaf04dc0431aaf4be9f3125dd9cfcb80f2ae7e25 (diff)
downloadrust-fe7254ff6f9ed485fe3d8b31c97c0beac1102d12.tar.gz
rust-fe7254ff6f9ed485fe3d8b31c97c0beac1102d12.zip
Auto merge of #8576 - smoelius:crate_in_macro_def, r=llogiq
Add `crate_in_macro_def` lint

This PR adds a lint to check for `crate` as opposed to `$crate` used in a macro definition.

I think this can close #4798. That issue focused on the case where the macro author "imports something into said macro."

But I think use of `crate` is likely to be a bug whether it appears in a `use` statement or not. There could be some use case I am failing to see, though. (cc: `@nilscript` `@flip1995)`

changelog: `crate_in_macro_def`
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp')
0 files changed, 0 insertions, 0 deletions