Lutz Hamel

We cannot use juxtaposition as a way to parameterize patterns, it makes the language too ambiguous due to the confusion with function application. We can adopt the generics notation here,...

The workaround is to put the pattern expression into parentheses, ``` for ((x,y) if x > y) in pairlist do assert(x>y). end ``` There is no good way to fix...

That's real bad. I thought, may be this is due to the way we might be interacting with Python but no, ``` lutz$ python3 Python 3.8.9 (default, Oct 26 2021,...

The function `isclose` already exists in our `math` module. Perhaps we should issue a warning when folks try to do an exact comparison on reals...

Yes! Actually even better, ``` Error: : 2: none of the function bodies unified with actual parameters foo "string!". .....^ ``` where it points to the offending token or structure....

I am not quite sure we want this...this is only needed when writing nested function definitions where the nested function uses data from the surrounding function definition as non-local data....

in 1.1.4 the generated error message reads ``` lutz$ asteroid loc.ast traceback (most recent call last): loc.ast: 1: calling loc.ast: 6: calling foo error: loc.ast: 2: actual argument 'string!' not...

The current approach to this is not unprecedented. Consider the following Python example, ``` >>> s = "0/0" >>> eval(s) Traceback (most recent call last): File "", line 1, in...

The reason why I ask that question is because the C compiler supports line directives. The C compiler could be compiling one file and you can make it think it...

We need to fix Asteroid's grammar to disallow with clauses with no statements. As a workaround, simply put the 'noop' statement -- a single period. ``` load system io. function...