"map" has become a keyword to introduce definition of maps by extension in declarations ("map" ... "end"). This entails that a grammar rule had to be created to handle the type expressions "map (..., ...)". Concordantly, I added map patches, modelled after record patches.
I created a node in the AST for map expressions (currently only
map look-ups).
I refactored the parser with parametric rules.
empty lists and None values as initial values in declarations.
Now, these values are accepted irrespective of the declared type. It
is up to the typechecker to validate them.
and "nothing".
Until now only products of type names were allowed: I extended
them to allow type expressions.
Removed the destructive update of a map binding "a[b] := c".
Record projection has been extended to allow for qualified
names: "a.b.c" and "a.b.c[d]".
Changed the LIGO extension from ".li" to ".ligo".
Fixed the name of the language to be "LIGO" (instead of "Ligo").
and functional update (copy).
The only creative piece of concrete syntax is that of the
expression for functional updates:
copy foo with record field = value end
where "copy", "with", "record" and "end" are keywords.
