diff options
| author | Son Ho | 2022-02-12 21:46:27 +0100 |
|---|---|---|
| committer | Son Ho | 2022-02-12 21:46:27 +0100 |
| commit | 65c60861d327a08ab8aee3ab122bcebeac5b8e7e (patch) | |
| tree | e2f68cc19f15bb372e245b780ca9ff89eed8919b /tests/hashmap | |
| parent | 3715d5ee40b4f217a49f4f144a4b96879525c9ef (diff) | |
Update some comments
Diffstat (limited to 'tests/hashmap')
| -rw-r--r-- | tests/hashmap/Hashmap.Properties.fst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/tests/hashmap/Hashmap.Properties.fst b/tests/hashmap/Hashmap.Properties.fst index ea021a95..7d695c12 100644 --- a/tests/hashmap/Hashmap.Properties.fst +++ b/tests/hashmap/Hashmap.Properties.fst @@ -131,9 +131,9 @@ module InteractiveHelpers = FStar.InteractiveHelpers /// extremely hard to debug. /// /// 1. See the comments for [hash_map_move_elements_fwd_back_lem_refin], which -/// are believe are quite instructive: I rarely note down the process of finding -/// a proof, but the comments for this one describe an experience which is very -/// similar to experiences I had before. +/// describe the various breakages I encountered, and the different attempts I +/// made to fix them (the result is that it now works, but I don't know why, and +/// there are still issues so it is maybe unstable).. /// /// Also, I still don't understand why the proof currently works, and failed /// before. One problem I encountered is that when trying to figure out why F* |