Andre Kuhlenschmidt

The following code failed at one point according to a comment in the make file that I am deleting. ```bash $ make -C src/backend/c/runtime test ```

```racket #lang typed/racket/no-check ;; The diffs between languages are one of the best sources of documentation ;; of what passes do to the language grammar that we currently have. ;;...

We tried using typed-racket, but the cost of ~1hr type-check times and the lack of full featured racket outweighs the benefit of types. Here is a plan for moving away...

I am not sure how to right a test to show this behavior but I don't think recursive types are not being hashconsed correctly. The equality test on recursive types...

We should have a style guide that extends the racket style guide. This could lead to higher coding quality.

The observation form was originally added because there wasn't any way of printing values. Now that we have basic printing we should consider removing the observation form which really doesn't...

The operations on types should be located in typed file near type-check.rkt

Every node in an AST should track its source location.

For instance ```racket (struct (Arity Args Ret) Fn ([arity : Arity][args : Args][ret : Ret])) ``` Should be instantiated up to the expression parameterization, and should have unneeded fields removed...