Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

One table-driven enclosing-scope and in-file test-scope walker instead of per-language copies

Open
  • Is something wrong?
#356 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp, csharp, javascript, kotlin, python, rust
Domain
cli, developer-experience, tooling

Research direction

Start in src/ingest_names.h by comparing the generic and per-language scope walkers, then read CONTRIBUTING §3 for the constexpr-table style. Use the existing gates, a before/after output map, and ripwire --clones to verify byte-identical results, removal of the duplicate group, and no new per-language functions.

Written by the indexing model from the issue text.

Description

enhancement help wanted

Part of the language-architecture cleanup tracked in #354 ("common stays common").

Problem. The same idea is written once per language in src/ingest_names.h:

  • enclosing scope: rustEnclosingScopeOf and kotlinEnclosingScopeOf are near-copies of the generic enclosingScopeOf (0.82 similar by ripwire --clones);
  • in-file test scope: four parallel *InFileTestScope functions (C#, JS, Python, Rust).

Change. One table-driven walker for each: a small constexpr per-language table (node kinds that open a scope, how the scope name is read, which nodes mark a test scope) and one function that reads it. The style rule is CONTRIBUTING §3, "Declarative constexpr tables over scattered switch/if".

Acceptance. Output byte-identical on every language (existing gates + a before/after map); ripwire --clones no longer reports the group; no new per-language functions.

Size: about a day. A good way to learn the ingest pipeline. Comment here to claim it.

Dominant language
C++
Stars
2.3k
Forks
145
Avg merge
8h 50m
Merged PRs (30d)
211

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from redhat-et/ripwire

All issues in redhat-et/ripwire

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.