rust-lang / rust-lang/rust

Tracking Issue for `const` `Clone`

Open
#142,757 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-tracking-issue S-tracking-needs-to-bake T-libs
Dominant language
Rust
Stars
119k
Forks
16.2k
PR merge metrics
PR metrics pending

Description

Feature gate: #![feature(const_clone)]

This is a tracking issue for making Clone a #[const_trait].

Public API

This should not change the public API.

Private API

This feature is not going to be stable for a long time. Instead it is mostly for internal use to facilitate other const implementations (e.g. #137843).

Care should be taken by those implementations to not inadvertently leak const Clone prior to stabilization.

Steps / History

(Remember to update the S-tracking-* label when checking boxes.)

  • Implementation: #142756
  • Final comment period (FCP)^1
  • Stabilization PR
Unresolved Questions
  • None yet.

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 with the const_clone feature gate and the implementation referenced as #142756, then review the tracking checklist and the stabilization guidance linked in the issue. The implementation is marked complete; remaining work is the final comment period and a stabilization PR, with no unresolved questions currently listed.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Feature
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.