rust/tests/ui/drop_bounds.stderr

error: bounds of the form `T: Drop` are useless, use `std::mem::needs_drop` to detect if a type has drop glue
  --> $DIR/drop_bounds.rs:2:11
   |
LL | fn foo<T: Drop>() {}
   |           ^^^^
   |
   = note: `#[deny(clippy::drop_bounds)]` on by default

error: bounds of the form `T: Drop` are useless, use `std::mem::needs_drop` to detect if a type has drop glue
  --> $DIR/drop_bounds.rs:5:8
   |
LL |     T: Drop,
   |        ^^^^

error: aborting due to 2 previous errors
Merge commit '09bd400243ed6f7059fedc0c1623aae3792521d6' into clippyup 2020-08-11 08:43:21 -05:00			error: bounds of the form `T: Drop` are useless, use `std::mem::needs_drop` to detect if a type has drop glue
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-16 22:28:16 -06:00			`--> $DIR/drop_bounds.rs:2:11`
			`\|`
			`LL \| fn foo<T: Drop>() {}`
			`\| ^^^^`
			`\|`
rustup https://github.com/rust-lang/rust/pull/62764 (was merged as part of https://github.com/rust-lang/rust/pull/62782 ) 2019-07-18 17:35:32 -05:00			= note: `#[deny(clippy::drop_bounds)]` on by default
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-16 22:28:16 -06:00
Merge commit '09bd400243ed6f7059fedc0c1623aae3792521d6' into clippyup 2020-08-11 08:43:21 -05:00			error: bounds of the form `T: Drop` are useless, use `std::mem::needs_drop` to detect if a type has drop glue
Fix formatting 2019-02-18 20:36:58 -06:00			`--> $DIR/drop_bounds.rs:5:8`
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-16 22:28:16 -06:00			`\|`
Fix formatting 2019-02-18 20:36:58 -06:00			`LL \| T: Drop,`
			`\| ^^^^`
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-16 22:28:16 -06:00
			`error: aborting due to 2 previous errors`