rust-lang / rust-lang/rust

Tracking Issue for `derive_from` (RFC 3809)

Open
#144,889 2 comments 30 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-tracking-issue F-derive_from T-compiler T-libs
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

This is a tracking issue for the RFC "3809" (https://github.com/rust-lang/rfcs/pull/3809).
The feature gate for the issue is #![feature(derive_from)].

About tracking issues

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 about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
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
  • Should we include the other direction of the From impl before we stabilize this?
Implementation history

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 RFC 3809 and the linked rustc-dev-guide stabilization and documentation instructions. Review the remaining checklist items for documentation, nightly syntax styling, Style Guide and rustfmt updates, and stabilization, then confirm the unresolved question about the reverse From implementation is addressed before the feature is complete.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.