Language testing

[dghosef]

This issue is for discussion of qdbp unit testing. We need testing framework(s) for qdbp, ocaml, and C components including

• parser
• lexer
• stdlib
• type checking
• codegen
• C runtime(hashmap, rc ops, arithmetic fns, etc)

We should also use some sort of static analysis on generated C code and UB sanitizers, memory sanitizers, etc. Also, make a pre-push hook that requires test to past

[dghosef]

One possible testing strategy: make qdbp's tests double as useful programs. For example,

• qdbp autoformatter(#47)
• qdbp red black tree + tests But run w/ sanitizers, etc of course

[dghosef]

In addition to end-to-end tests we should also test unusual cases that won't happen much. Including

• Rigorous testing for 63 bit overflow handling
• Testing of invoking, extension and replacement for channels, strings, bools, and ints
  • Try extending ints with bool operators and bools w/ int operators to make sure there's no confusion

[dghosef]

We also need tests for the type system - that we error when we should and don't error when we should

[dghosef]

To test associativity we should have programs that typecheck only when associativity is correct