lean4-htt/tests
Leonardo de Moura 3651dc7618 feat(library/init/lean): add evalConst
The implementation is good enough for implementing extensible parsers,
elaborators and tactics, but there are a few TODOs

1- We should have a better story for standalone applications.
   Most of them don't need `evalConst`, and the global table is
   just initialization overhead.

2- The global table introduces a dependency on the `Lean.Name`
   implementation. So, all standalone applications will depend on it.

3- We are not storing arity 0 constants in the table.
   This one should be easy to fix in the future.
2019-06-07 16:31:28 -07:00
..
bench chore(tests/bench): further tweak Swift support 2019-05-31 10:48:50 +02:00
compiler feat(library/init/data/string): add String.isPrefixOf 2019-06-06 14:20:50 -07:00
ir chore(tests): port tests, fix at least compiler tests 2019-03-21 15:11:05 -07:00
lean chore(tests/lean): remove/fix tests 2019-06-07 09:56:11 -07:00
playground feat(library/init/lean): add evalConst 2019-06-07 16:31:28 -07:00