Surface OMD Errors with line number
Open
Nobody has claimed this yet.
- Dominant language
- Reason
- Stars
- 66
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
While compiling, getting a nice error telling me what line number is the broken one seems ideal to fix it quickly.
Contributor guide
No contributing guide indexed for this repository
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
Start by locating the OMD compilation and error-reporting path. Reproduce a compilation failure with a known malformed input, then trace how the error is surfaced. Done means compiler errors identify the line number of the broken input clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100