rust-lang / rust-lang/rust

Tracking issue for MCP 904: Experiment with replacing specialization in libcore with downcasting

Open
#149,242 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

B-MCP-approved C-tracking-issue S-tracking-unimplemented T-compiler
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

This is a tracking issue for MCP "Experiment with replacing specialization in libcore with downcasting" (rust-lang/compiler-team#904).

[!NOTE]
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.

A tracking issue is however not meant for large scale discussion, questions, or bug reports.
Instead, open a dedicated issue for the specific matter, link to this tracking issue and ping the MCP author.
Alternatively, post in the Zulip stream linked from the MCP.

Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Steps
Unresolved questions

None so far.

Implementation history

Empty so far.


@oli-obk, consider @rustbot claim'ing the work.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading MCP rust-lang/compiler-team#904, which defines the experiment of replacing specialization in libcore with downcasting. Check the Rust Compiler Development Guide, Rust Forge, and rustc book for documentation affected by the change. Done means the MCP is implemented and applicable documentation updates are completed.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.