microsoft / microsoft/cmd-call-graph
Track the terminating vs. non-terminating code paths for a given node
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 59
- Forks
- 23
- Avg merge
- 16h 39m
- Merged PRs (30d)
- 1
Description
A node can be both terminating and non-terminating, depending on how it's invoked.
If it's reached via goto or nested from a node that would have been terminating, it's terminating for that code path. But if it's reached via call from a non-terminating node, it's not terminating.
It would be nice to surface this information somehow. The easiest option might be a warning, not sure how to actually represent this case in the call graph.
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, test, or entry point is named. Start by tracing how goto, nested, and call edges are represented in the call graph, then determine how terminating status could be surfaced and define a testable representation or warning for the two code paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100