Uplift drop-bounds lint from clippy into rustc

[notriddle]

Proposal

Move the drop_bounds lint from clippy into the compiler. The lint would be warn by default, and fire when generic bounds require a type to implement Drop.

For instance, the following code

fn do_something<T: Drop>(_x: T) { }

would trigger the lint. This pattern is, as ExpHP put it, dangerous and wrong, as well as a common tripping point for newbies, so it would be ideal for the compiler to help prevent this particular footgun.

Mentors or Reviewers

I've performed this change on rust-lang/rust#75699 CC @petrochenkov

Process

The main points of the Major Change Process is as follows:

• File an issue describing the proposal.
• A compiler team member or contributor who is knowledgeable in the area can second by writing @rustbot second.
  • Finding a "second" suffices for internal changes. If however you are proposing a new public-facing feature, such as a -C flag, then full team check-off is required.
  • Compiler team members can initiate a check-off via @rfcbot fcp merge on either the MCP or the PR.
• Once an MCP is seconded, the Final Comment Period begins. If no objections are raised after 10 days, the MCP is considered approved.

You can read more about Major Change Proposals on forge.

Comments

This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

[rustbot]

This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

[pnkfelix]

@rustbot second