rust-lang / rust-lang/rfcs

Make debug info available programatically

Open
#476 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Probably using macros.

Tracking issue for #468

cc @mitsuhiko (I hope I have got the title about right as a slightly more general version of your RFC, let me know if you think there should be a better title.

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 reading the linked tracking issue #468 and the surrounding RFC discussion; this issue names no files, tests, or implementation entry point. Done would require a settled design for exposing debug information programmatically, followed by an agreed implementation and validation plan.

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
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.