det translator: more readable Java — extend provably-safe lifting from bytes to plain Java types
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
Start with the lift criteria in program.py, since the issue says the translator already lifts some fields to plain Java types under them, and check how REDEFINES and group MOVEs are currently treated. The work needs a per-port readability metric recorded in the evidence report before any lifting changes. Done means the full det sweep and fuzz run show 0 verdict diffs, and each new lift has a recorded safety reason.
Written by the indexing model from the issue text.
Description
What. COBOL programs often reinterpret the same bytes (REDEFINES, group MOVEs), so faithful ports keep byte-exact storage, which produces hard-to-read Java. The translator already lifts some fields to plain Java types when that's provably safe (program.py lift criteria). Extend this: more field kinds, local reasoning about REDEFINES and group use, and readable names.
Measure readability per port: share of fields lifted, runtime calls per statement, method sizes. Track it in the evidence report.
Acceptance.
- A readability metric per port.
- An increase on the burned estates.
- No verdict change: full det sweep, fuzz 0 diffs.
- Every lift is justified by a recorded safety reason.
Part of the cobolrt-as-a-product epic (linked from the epic). Owner-approved direction, 2026-10-08.
🤖 Generated with Claude Code
- 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