rust-lang / rust-lang/rfcs

Proposal: Std: Compile-time reflection.

Open
#2,743 15 comments 25 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-reflection T-lang
Dominant language
Markdown
Stars
6.6k
Forks
1.7k
Avg merge
16h 14m
Merged PRs (30d)
1

Description

Goal is to have ability to generate descriptive struct by macro(from std).

Reason is that in lot of crates there are impementations of compile time reflection not compatible with each other, so many developers just reinventing wheel.

Proposed features:

  1. The Reflector trait in std.
  2. Implementation of derive macro.
  3. Unsafe fn's to acess fields by name.
  4. (Optional) Mechanism to store metadata of/for fields.

P.S I won't propose implementation, because i can't imagine brige between compile time generics and runtime logic.

Contributor guide

No contributing guide indexed for this repository

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 reviewing the proposed Reflector trait, derive macro, unsafe field access functions, and optional field metadata mechanism in the issue. No files, tests, or implementation entry points are named; the work is done only after the scope and design bridge between compile-time generics and runtime logic are defined.

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.