Figure out all debugging information representations of statements
Open
Nobody has claimed this yet.
A-debuginfo
A-mir-opt
C-tracking-issue
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
#142771 has eliminated the simple reference assignment statement. We should figure out more about how to represent others statements via debugging information.
Steps
- How to represent projection of place, i.e.,
_1.1 = &_2;? - How to represent other rvalues?
- Other non-assignment statements?
Implementation history
#142771 has implemented _1 = &_2.
Related Resources
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the implementation history in #142771 and the linked LLVM Debug Info Assignment Tracking and Source Level Debugging resources. Compare their treatment of simple assignments with the projection, other rvalue, and non-assignment cases listed here. Done means establishing and documenting representations or implementation plans for the remaining checklist items.
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
- 25/100