leanprover / leanprover/lean4-cli
Avoiding manual conversion step & autocompletion
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 120
- Forks
- 30
- Avg merge
- 5m
- Merged PRs (30d)
- 4
Description
When I have time to work on this again (in ~2 months), I'd like to adjust the API so that no extra conversion step is necessary at the end and work on autocompletion.
For the former, a macro approach could work well, where a type-safe output structure is generated either from a Parsed value or even directly at the start using the configuration macro. The library does not really track the real type right now, so the latter should be safer.
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 reading the library's current API around Parsed values, configuration macros, and the final conversion step. Define completion as a type-safe output structure that removes the extra conversion and adds autocompletion, but the issue does not name files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100