leanprover-community / leanprover-community/lean
Fix warnings
Open
Nobody has claimed this yet.
build
- Dominant language
- C++
- Stars
- 434
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
Description
This is a tracking issue for cleaning up warnings in the lean build (or determining that they can't be fixed).
Contributor 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.
Research direction
Start by running the Lean build and recording the warnings it produces. Review each warning to determine whether it can be fixed; done means the warnings are cleaned up or the remaining unfixable warnings are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100