Mainly in loops, reducing the amount of hashtable resolutions will improve performance
Contributor guide
Tech stack
c
Domain
cliperformance
Issue type
performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
C programmingradare2 codebaseRConfig API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
First, identify all occurrences of RConfig.get() inside loops across the radare2 source code. Use tools like grep to find these patterns. Evaluate each occurrence to determine if the call can be hoisted outside the loop or if the value can be cached. Consider the impact on performance and correctness. Check if there are any existing tests or comments related to these calls.
Remove unnecessary calls to RConfig.get · radareorg/radare2#13499 | Good First Issue
