| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2019-02-18 | Fix formatting | Michael Howell | -1/+5 | |
| 2019-02-17 | Add a lint to warn on `T: Drop` bounds | Michael Howell | -0/+4 | |
| **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>() {} ``` | ||||
