One shared inert-region mechanism (quote, discard, comment forms) instead of per-language checks
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 68/100
Research direction
Start by reading src/ingest_elixir.h, especially elixirQuoted, and compare it with clojureQuotedOrDiscarded from #349; then inspect the shared vocabulary in tags.scm. Add the red-first gate using the quoted-call fixture for Elixir, verify inert references produce no call edges but are counted, and confirm other languages remain byte-identical.
Written by the indexing model from the issue text.
Description
Part of the language-architecture cleanup tracked in #354 ("common stays common").
Problem. "Calls inside quoted or commented-out code are not calls" is one idea, written per language: Elixir quote do … end (elixirQuoted in src/ingest_elixir.h), and in #349 Clojure's '/`/#_ (clojureQuotedOrDiscarded), soon also Clojure (comment …) blocks.
Change. One shared inert-region mechanism: either a capture in the shared vocabulary (e.g. @inert in tags.scm) or one per-language hook with a single call site. References inside an inert region mint no call edges and are counted, not silently dropped.
Acceptance. A gate, red first, with a quoted-call fixture for Elixir (and Clojure once #349 lands); every other language byte-identical.
Size: 0.5–1 day. Comment here to claim it.
- Dominant language
- C++
- Stars
- 2.3k
- Forks
- 145
- Avg merge
- 8h 53m
- Merged PRs (30d)
- 212
Getting set up
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.
More from redhat-et/ripwire
-
Difficulty 2/5 Under an hour Newbie friendliness 78/100
redhat-et/ripwire#334 · 7 comments ·
Maintainers usually reply within 1 day
-
help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
redhat-et/ripwire#68 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
nightly-failure nightly-full-matrix
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
All issues in redhat-et/ripwire
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mpfaffenberger/privateer_reimagined#658 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
microsoft/onnxruntime#33018 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
AXERA-TECH/ax-llm#81 ·
-
enhancement
Difficulty 2/5 Half a day Newbie friendliness 78/100
ros-industrial/ros2_canopen#448 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day