Remove overriding impls of deprecated `Error::description`.

[hkBst]

Proposal

Remove overriding impls of deprecated Error::description.

I naively proposed removing one such here as I was under the mistaken impression that it would delegate to Display::fmt, but it actually defaults to "description() is deprecated; use Display".

Deprecation happened 46 stable versions ago (in 1.42), or almost 6 years ago.

git grep 'fn description' | wc -l currently gives 72 results, which would need to be changed.

Mentors or Reviewers

The change itself is not very hard, so I could mentor or do this myself.

Process

The main points of the Major Change Process are 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.

[rustbot]

Important

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.

Concerns or objections can formally be registered here by adding a comment.

@rustbot concern reason-for-concern
<description of the concern>

Concerns can be lifted with:

@rustbot resolve reason-for-concern

See documentation at https://forge.rust-lang.org

cc @rust-lang/compiler

[jieyouxu]

Hi, thanks for the proposal. However, this change does not fall under the purview of the compiler team, and it instead concerns the Library API team. The suitable avenue for this proposal is an API Change Proposal against the libs-team repository.

[hkBst]

@jieyouxu Sorry about that, and thanks for pointing me in the right direction.