Lean 4 fork for HoTT-compatible kernel extensions (Path types, transport, HITs). Maintained against upstream leanprover/lean4.
0dcdc2c198
@kha, the implementation is a little bit hackish. It is whitespace sensitive to avoid `f @g`, an application with argument `@g` to be parsed as a named pattern. Here are other approaches I have considered: 1- In the `namedPattern`, we add a guard that ensures the pattern is *not* an identifier. Thus, `f @g` would not be considered a valid `namedPattern`. Drawback: we would always try to parse it as a namedPattern first, fail, and then try as an application. 2- Enforce whitespace before application arguments. Drawback: `f(a+b)` would not be a valid application anymore. |
||
|---|---|---|
| .github | ||
| bin | ||
| doc | ||
| images | ||
| lean4-mode | ||
| library | ||
| script | ||
| src | ||
| tests | ||
| tmp/new-frontend | ||
| .appveyor.yml | ||
| .clang-format | ||
| .codecov.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .travis.yml | ||
| azure-pipelines.yml | ||
| default.nix | ||
| derivation.nix | ||
| LICENSE | ||
| README.md | ||
| shell.nix | ||
We are currently developing Lean 4. Lean 3 is still the latest official release. This repository contains work in progress.
Important. Unless you are one of our collaborators
- We strongly suggest you use Lean 3.
- Pull requests are not welcome.
- New issues are not welcome, and will be closed without any feedback.