diff options
author | Josh Chen | 2020-06-01 17:22:09 +0200 |
---|---|---|
committer | Josh Chen | 2020-06-01 17:22:09 +0200 |
commit | cf5136f00a5eaa0f81cb84705db04171a614c43a (patch) | |
tree | 0881af46eecdcc6f3daab48e2a15fb93655a6923 | |
parent | 29112d66eb3ecf4139db1da16878d8a817640696 (diff) |
update
-rw-r--r-- | README.md | 13 |
1 files changed, 7 insertions, 6 deletions
@@ -20,10 +20,11 @@ $ echo path/to/Isabelle/HoTT >> ~/.isabelle/Isabelle2020/ROOTS In no particular order. Some of the following might require changes to the Isabelle prover itself. -[ ] Typing information is implicit in context facts, and the collection must be searched every time we need a type for a term. - For performance, should probably implement dedicated tables. -[ ] Tactic-based term elaboration has (at least) two problems: 1. `assume(s)` clauses don't accept schematic vars, and 2. it often results in overly-flexible subgoals that the typechecker doesn't solve. - Will likely need an elaborator integrated into Isabelle's syntax checking. -[ ] Inductive type definitions. -[ ] Recursive function definitions. +- [ ] Implement dedicated tables for type information. +- [ ] Tactic-based term elaboration has (at least) two problems: + 1. `assume(s)` clauses don't accept schematic vars, and + 2. it often results in overly-flexible subgoals that the typechecker doesn't solve. + Will need an elaborator integrated into Isabelle's syntax checking. +- [ ] Inductive type definitions. +- [ ] Recursive function definitions. |