You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2022. It is now read-only.
Similar to #639: now that we're exporting Util/, it would be nice to clean it up a bit. This issue tracks those efforts.
Remove experimental code and unused definitions (unused lemmas can stay)
Write tests for all tactics
Organize files more logically
A bit more on the last point: many files in Util (looking at you, Vector.v) contain proofs and code interleaved chaotically. Any consistent structure is a good structure, but my first suggestion for Util files would be the style in List.v, with a separate section for each definition and its proofs, or just the proofs if it's from the standard library. Example snippet illustrating the pattern:
At this point we have cava2 succeeding cava but depending on it for Cava/Util. AFAIK Cava/Util has no dependencies and could be made into a standalone library.
At this point we have cava2 succeeding cava but depending on it for Cava/Util. AFAIK Cava/Util has no dependencies and could be made into a standalone library.
Similar to #639: now that we're exporting
Util/
, it would be nice to clean it up a bit. This issue tracks those efforts.A bit more on the last point: many files in
Util
(looking at you,Vector.v
) contain proofs and code interleaved chaotically. Any consistent structure is a good structure, but my first suggestion forUtil
files would be the style inList.v
, with a separate section for each definition and its proofs, or just the proofs if it's from the standard library. Example snippet illustrating the pattern:silveroak/cava/Cava/Util/List.v
Lines 164 to 227 in b0dc9fd
The text was updated successfully, but these errors were encountered: