lambdaclass / lambdaclass/lambda_compiler_kit
refactor: separate proof/spec files into a dedicated LckSpec lake target
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Problem
Spec and proof files (RegexSpec.lean, DesugarSpec.lean, ParserSpec.lean, etc.) are included in the main Lck library target. This means every downstream user of the library also compiles the proof infrastructure, which is heavyweight (imports Mathlib, long compile times).
Expected fix
Move spec/proof files into a separate LckSpec Lake target (or library) that is only built when explicitly requested (e.g., for verification or CI). The main Lck target should contain only the runtime-relevant code.
References
- Suggested by AI code review on PR #9
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
Inspect the current Lake target definition and the listed spec/proof files, including RegexSpec.lean, DesugarSpec.lean, and ParserSpec.lean. Confirm which files are pulled into the main Lck target, then separate them into an explicitly built LckSpec target while keeping runtime-relevant code in Lck. Done means downstream builds of Lck no longer compile the proof infrastructure, while LckSpec remains available for verification or CI.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, compilers
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100