Introduce STOP_WALK and CONTINUE_WALK macros for better readability
Open
- Dominant language
- C
- Stars
- 12.8k
- Forks
- 794
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 31
Description
https://github.com/citusdata/citus/pull/4326#discussion_r529305084
Contributor guide
Research direction
Start with the pull request discussion linked in the issue and identify the C code and walk logic it refers to. Confirm which existing control-flow cases should use STOP_WALK and CONTINUE_WALK, then verify that the macros improve readability without changing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, postgresql
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100