software-mansion / software-mansion/cairo-debugger
Verify if it makes sense to ignore variables produced by `Return` statements
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7
- Forks
- 2
- Avg merge
- 5d 2h
- Merged PRs (30d)
- 1
Description
As in the title. It seems to make sense since right after return (in Sierra) we exit the function we are in anyways, so it doesn't affect what the user sees (while simplifying the code).
Contributor guide
No contributing guide indexed for this repository
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
No file or test is named. Start by locating how Return statements and their produced variables are handled in the debugger, then check the corresponding Sierra control-flow behavior. Done means reaching and documenting a clear decision on whether those variables can be ignored without changing what users observe.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, devtools
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100