11 commits

Author	SHA1	Message	Date
Yuki Okushi	a4c201e6b4	Rustup to rust-lang/rust#66942	2019-12-30 13:02:10 +09:00
Matthias Krüger	98e433d70d	Rustup to rust-lang/rust#66878	2019-12-04 01:34:01 +01:00
Oliver Scherer	f7f85a0dca	Prevent symbocalypse	2019-05-17 23:53:54 +02:00
Oliver Scherer	dfbc74b08b	Rustfmt all the things	2019-05-14 10:33:48 +02:00
Oliver Scherer	b2dbda4d48	Use symbols instead of strings	2019-05-14 10:33:42 +02:00
Matthias Krüger	d618637c05	Rustup to rustc 1.36.0-nightly (13fde05b1 2019-05-03)	2019-05-03 22:28:34 -07:00
Matthew Kraai	753c39672e	Use lint pass macros ... Fixes #3917.	2019-04-17 09:35:22 -07:00
flip1995	840eac2c05	Use {get,match}_def_path from LateContext	2019-04-17 12:53:29 +02:00
Andy Russell	fe96ffeac9	move lint documentation into macro invocations	2019-03-05 18:45:08 -05:00
Michael Howell	bc4c3b6ff1	Add more descriptive details	2019-02-18 19:37:08 -07:00
Michael Howell	2df14c3701	Add a lint to warn on T: Drop bounds ... **What it does:** Checks for generics with `std::ops::Drop` as bounds. **Why is this bad?** `Drop` bounds do not really accomplish anything. A type may have compiler-generated drop glue without implementing the `Drop` trait itself. The `Drop` trait also only has one method, `Drop::drop`, and that function is by fiat not callable in user code. So there is really no use case for using `Drop` in trait bounds. **Known problems:** None. **Example:** ```rust fn foo<T: Drop>() {} ```	2019-02-17 22:53:08 -07:00