Torin Sandall 7ca542adb5 Refactor functions implementation ...

Previously, functions were implemented with a separate set of types that
had their own code paths in the compiler, eval, etc. These changes
refactor the function implementation so that functions are implemented
as rules with one or more arguments.

By representing functions as rules, we can avoid special casing required
to support functions, e.g., during parse and compile there are a number
of steps that required special casing for functions:

- Parser needed separate grammar definitions for functions (which
  prevented them from being chained or using else)

- Compiler needed separate resolver and type checker implementations
  which was a source of bugs.

In some cases, special casing is unavoidable for now (e.g., during eval)
however this could be improved in the future.

Fixes #471
Fixes #467
Fixes #463

2017-10-10 08:57:58 -07:00

..

errors.go

Update error codes and messages throughout

2017-02-16 10:29:57 -08:00

example_test.go

Add support to cancel compilation after some number of errors

2017-07-21 07:59:51 -07:00

repl_test.go

Refactor functions implementation

2017-10-10 08:57:58 -07:00

repl.go

Refactor functions implementation

2017-10-10 08:57:58 -07:00