Oliver McLaughlin

We need a comprehensive way of testing the REPL. For right now, that basically means testing: 1. Simple statements 2. Multiline statements

issue warning when user performs an exact comparison on reals

3

Because python's underlying floating point arithmetic has precision errors, the following program prints out false: ``` load system io. io @println ( (.1 + .1 + .1) == .3 )....

Locational error reporting

3

Consider the program: ``` function foo with x:%integer do return 1. end foo "string!". ``` Running this would return the error `Error: : 2: none of the function bodies unified...

The debugger needs a test suite to make sure every feature is working correctly.

Make note in documentation about possible errors in patterns

1

Since users are able to construct possibly error containing patters, we need to note in the documentation that things like: ``` structure B with data a. data b. end --...