lean4-htt/tests
Joachim Breitner 17825bf81d
feat: GuessLex: if no measure is found, explain why (#2960)
by showing the matrix of calls and measures, and what we know about that
call (=, <, ≤, ?), e.g.

guessLexFailures.lean:27:0-33:31: error: Could not find a decreasing
measure.
    The arguments relate at each recursive call as follows:
(<, ≤, =: relation proved, ? all proofs failed, _: no proof attempted)
               x1 x2 x3
    1) 29:6-25  =  =  =
    2) 30:6-23  =  ?  <
    3) 31:6-23  <  _  _
    Please use `termination_by` to specify a decreasing measure

It’s a bit more verbose for mutual functions.

It will use the user-specified argument names for functions written
```
foo (n : Nat) := …
```
but not with pattern matching like
```
foo : Nat → … 
  | n => …
```
This can be refined later and separately (and maybe right away in
`expandMatchAltsWhereDecls`).
2023-12-05 08:32:15 +00:00
..
bench chore: add import Lean benchmark 2023-11-07 18:46:28 +01:00
compiler feat: allow trailing comma in tuples, lists, and tactics (#2643) 2023-11-17 13:31:41 +01:00
elabissues chore: fix more typos in comments 2023-10-08 14:37:34 -07:00
ir
lean feat: GuessLex: if no measure is found, explain why (#2960) 2023-12-05 08:32:15 +00:00
pkg chore: ignore forgotten Lake test artifacts 2023-11-17 21:25:41 -05:00
playground perf: Use flat ByteArrays in Trie (#2529) 2023-09-20 13:22:37 +02:00
plugin feat: profiling of linters 2023-04-18 15:30:21 +02:00
simpperf
.gitignore
common.sh fix: use -O3 for LLVM tests in common.sh 2023-11-02 23:21:47 +01:00
lean-toolchain doc: VS Code dev setup (#2961) 2023-11-30 08:35:03 +00:00