Pseudocode and disassemble issues
Nobody has claimed this yet.
- Dominant language
- Macaulay2
- Stars
- 435
- Forks
- 297
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 11
Description
Remaining tasks from https://github.com/Macaulay2/M2/issues/3395#issuecomment-2277134043:
1. rename `Pseudocode -> PseudocodeBody`, add `Pseudocode` as common parent to parallel `Function/FunctionBody/FunctionClosure`.
2. combine `functionBody` and `symbolBody` and have it return the inner "body" of symbols, functions, and pseudocodes.
3. make `Pseudocode` objects easily traverseable (mainly getting `#` methods to work)
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
Read issue #3395 and its referenced comment first, then trace the Pseudocode, PseudocodeBody, Function, FunctionBody, and FunctionClosure concepts. Review how functionBody and symbolBody currently behave before consolidating them. Done means the hierarchy is renamed and unified, inner bodies are returned consistently, and Pseudocode objects support traversal including # methods.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100