matthiaskrgr / matthiaskrgr/icemaker
find out broken-file to broken-file diagnostics
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 88
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
run rustc before, note all the errors
run cargo fix --broken code to a new file
if the file changed (hints were applied) and the file is not fixed yet, we know error hints failed
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 running rustc on a broken file and recording all diagnostics, then run cargo fix --broken against a separate output file. Compare whether the file changed and whether it is fixed; done means the comparison identifies cases where applied hints fail to resolve the errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100