Lean 4 fork for HoTT-compatible kernel extensions (Path types, transport, HITs). Maintained against upstream leanprover/lean4.
2075103cd9
This PR surfaces kernel diagnostics even in `example`. The problem was that the kernel checking happens asynchronously. We cannot use `reportDiag` in `addDecl`, which spawns that task, due to the module hierarchy. For non `example`-declaration, `reportDiag` is called somewhere else later, but for `example`, the `withoutModifyingEnv` in `elabMutualDef` hid the kernel diagnostics. (But only the kernel diagnostics; they are in the `Environment`, while the others are in the `State`). I also observed that the `reportDiag` in `elabAsync` (but not in `elabSync`) duplicated the reporting, so without `elab.Async true` you get the message twice. To fix this, `reportDiag` now resets the diagnostics. This should avoid reporting counts twice in general (at least within a linear use of the state). --------- Co-authored-by: Sebastian Ullrich <sebasti@nullri.ch> |
||
|---|---|---|
| .github | ||
| doc | ||
| images | ||
| nix | ||
| releases_drafts | ||
| script | ||
| src | ||
| stage0 | ||
| tests | ||
| .gitattributes | ||
| .gitignore | ||
| .gitpod.Dockerfile | ||
| .gitpod.yml | ||
| .ignore | ||
| CMakeLists.txt | ||
| CMakePresets.json | ||
| CODEOWNERS | ||
| CONTRIBUTING.md | ||
| flake.lock | ||
| flake.nix | ||
| lean-toolchain | ||
| lean.code-workspace | ||
| LICENSE | ||
| LICENSES | ||
| README.md | ||
| RELEASES.md | ||
This is the repository for Lean 4.
About
- Quickstart
- Homepage
- Theorem Proving Tutorial
- Functional Programming in Lean
- Documentation Overview
- Language Reference
- Release notes starting at v4.0.0-m3
- Examples
- External Contribution Guidelines
Installation
See Setting Up Lean.
Contributing
Please read our Contribution Guidelines first.
Building from Source
See Building Lean.