leanprover-community / leanprover-community/lean

a flag to stop `lean --make` at the first error

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

Nobody has claimed this yet.

enhancement
Dominant language
C++
Stars
434
Forks
79
PR merge metrics
No merged PRs in 30d

Description

When I call lean --make I often don't care about the full output; either it succeeds, or there's an error, and I want to start fixing from the first error. Would it be possible to add a flag that would stop the build as soon as something goes wrong?

mathlib pipes the build into a Python script to short circuit on errors, and I'd like to duplicate that behavior in other CI in a less hackish way.

Prerequisites
  • Put an X between the brackets on this line if you have done all of the following:
    • Checked that your issue isn't already filed.
    • Reduced the issue to a self-contained, reproducible test case.
Description

[Description of the issue]

Steps to Reproduce
  1. [First Step]
  2. [Second Step]
  3. [and so on...]

Expected behavior: [What you expect to happen]

Actual behavior: [What actually happens]

Reproduces how often: [What percentage of the time does it reproduce?]

Versions

You can get this information from copy and pasting the output of lean --version,
please include the OS and what version of the OS you're running.

Additional Information

Any additional information, configuration or data that might be necessary to reproduce the issue.

Contributor guide

Open the contributing guide

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.

Research direction

Start by locating the lean --make command entry point and compare its behavior with the mathlib Python script mentioned in the issue. Done means a supported flag stops the build at the first error, with the behavior verified for the command's failure path.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
build-system, cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.