4 commits

Author	SHA1	Message	Date
Matthias Krüger	0db5cb1393	drop_bounds: make lint adhere to lint message convention	2020-08-10 23:49:06 +02:00
Matthias Krüger	deb586a0c6	rustup https://github.com/rust-lang/rust/pull/62764 ... (was merged as part of https://github.com/rust-lang/rust/pull/62782 )	2019-07-19 00:35:32 +02:00
Michael Howell	2da7f084fe	Fix formatting	2019-02-18 19:36:58 -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