Lean 4 fork for HoTT-compatible kernel extensions (Path types, transport, HITs). Maintained against upstream leanprover/lean4.
f0ebf426b7
Before this commit, we were handling the following two abnormal cases: 1- `p` did not produce any `Syntax` node. `runLongestMatchParser` would insert a `Syntax.missing`. 2- `p` produced more than one `Syntax` node on the stack. `runLongestMatchParser` would combine all of them using a `nullKind` node. This feature was never used since we only use `longestMatchFn` to process leading and trailing parsers. In both case, we create a node. Moreover, if a bad parser is manually created, I think it is better to fail than accept using `Syntax.missing` or a `nullKind` node. We would only be postponing the problem since we don't have elaboration functions for them. cc @Kha |
||
|---|---|---|
| .github | ||
| doc | ||
| images | ||
| lean4-mode | ||
| nix | ||
| script | ||
| src | ||
| stage0 | ||
| tests | ||
| tmp | ||
| .clang-format | ||
| .codecov.yml | ||
| .gitattributes | ||
| .gitignore | ||
| CMakeLists.txt | ||
| default.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.