drm: don't walk every path if filter option was used
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 200
- Forks
- 85
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 2
Description
We may not need to walk every path if some can be excluded based on the --match or --exclude options that were specified. For instance, if the user is searching for *.txt files in the current working directory do we need to walk all of the subdirectories?
Contributor guide
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 source files or tests are named. Start by tracing how the utility handles --match and --exclude while walking paths, then identify where excluded subdirectories can be skipped. Done means matching behavior remains correct while irrelevant subtrees are not traversed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100