Siblings of #3799: call-graph engine defects (dart, haskell, c++, rust)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start with the verdict slice in PR #6453 and the parent issue #3799 to understand how the call-graph engine compares against tree-sitter. Reproduce the listed Dart, Haskell, and Rust cases, then trace their parser or call-graph handling; the C++ item is already fixed in #6524. Done when the remaining listed defects are corrected and the verdict slice confirms the expected call-graph results.
Written by the indexing model from the issue text.
Description
Siblings of #3799: engine defects confirmed by the verdict slice in PR #6453 (call-graph, tree-sitter comparison). No burned-estate program needs these.
- dart: generic invocations
f<T>(x)are dropped (shapeargument_part/-+generic, 88) (#6550) - dart: type names in optional/named parameter lists counted as callees (
formal_parameter<optional_formal_parameters, 51) (#6550) - haskell: function application by juxtaposition missed (
apply/variable68,apply/apply53) - haskell: constructor application missed (
apply/constructor69) - c++: declared type names with
=initializers counted as callees (declaration<compound_statement; constructor-style initializers are correct) (#6524) - rust: tokens in pattern positions inside
matches!-style token trees counted as calls (token_tree<macro_invocation; sibling shapetoken_tree<token_tree47 still open)
Part of #3799.
- Dominant language
- Python
- Stars
- 57
- Forks
- 11
- Avg merge
- 1h 35m
- Merged PRs (30d)
- 975
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from squid-protocol/gitgalaxy
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
squid-protocol/gitgalaxy#7827 · 1 comment ·
Maintainers usually reply within 1 day
-
scope:frontier
Difficulty 5/5 Over a week Newbie friendliness 18/100
squid-protocol/gitgalaxy#7900 ·
Maintainers usually reply within 1 day
-
core-engine scope:infra testing
Difficulty 4/5 3-5 days Newbie friendliness 54/100
squid-protocol/gitgalaxy#7863 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
squid-protocol/gitgalaxy#7834 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 56/100
squid-protocol/gitgalaxy#7828 · 1 comment ·
Maintainers usually reply within 1 day
All issues in squid-protocol/gitgalaxy
Similar issues
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
graphql-python/graphql-core#304 ·
Maintainers usually reply within 1 day
-
docs size:S
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Gathin23/cleanyourtv#3464 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day