Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Avoiding manual conversion step & autocompletion

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
cli

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.

Description

enhancement

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.

Dominant language
Lean
Stars
120
Forks
30
Avg merge
5m
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from leanprover/lean4-cli

All issues in leanprover/lean4-cli

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.