lean4-htt/tests/lean
Leonardo de Moura acade175b6 feat(library/init/data/array): store dimension in the array
The array dimension is now stored inside the array.
The main motivation is that it reflects the actual runtime implementation.
We need to store the array size to be able to GC it.
So, it feels silly to have the array size stored in each array object,
but we cannot use this information.
For example, in the `hashmap` we implemented the bucket array using
`array`, and we store the `size` of the array.
Same for the Lean3 `buffer` object.
The `buffer` object doesn't even need to exist.
The actual `array` implementation is the `buffer`
2018-05-03 15:43:03 -07:00
..
fail
run feat(library/init/data/array): store dimension in the array 2018-05-03 15:43:03 -07:00
trust0 fix(tests/lean/trust0/basic): test 2018-04-30 10:13:35 -07:00
check.lean
check.lean.expected.out
extract.lean chore(tests/lean): restore string tests 2018-04-26 17:36:41 -07:00
extract.lean.expected.out feat(library/vm/vm_string): add fast string.iterator.remaining 2018-04-26 18:03:41 -07:00
parser1.lean chore(tests/lean/parser1): fix test 2018-05-02 17:37:55 -07:00
parser1.lean.expected.out test(tests/lean/parser1): add parser tests 2018-04-28 15:58:50 -07:00
readlinkf.sh
string_imp.lean feat(library/init/data/string/basic): add string.line_column 2018-04-30 15:55:34 -07:00
string_imp.lean.expected.out chore(tests/lean/string_imp): fix test 2018-04-30 16:15:51 -07:00
string_imp2.lean chore(tests/lean): restore string tests 2018-04-26 17:36:41 -07:00
string_imp2.lean.expected.out chore(tests/lean): restore string tests 2018-04-26 17:36:41 -07:00
test.sh
test_all.sh
test_single.sh
test_single_pp.sh