Peter Podlovics

> ``` > named case scrutinees > named node fields > name function arguments > named store argument > ``` > > Please could you give examples how they are...

> ``` > data FName > = F { fName :: Name } > | E { fname :: Name } > ``` > > How FName will fit to...

> Last return > > Lets use the `pure` as it is already established in the syntax, as also doesn't give the > false sense of return point of a...

> ``` > Program, function, definition > The above mentioned notions should be different syntactic constructs. > ``` > > This design decision was taken to be compatible with the...

Exactly. Constants could only be introduced in the above form. Everywhere else, we would be just passing variables around.

The __separation of__ external and ordinary __function application has been scrapped__. The reason being is that it makes writing code for function application cumbersome. Whenever we need the fact that...

Extended the proposal with the __removal of low-level GRIN construct__. `VarTag` node and indexed `Fetch` will be removed. These constructs were originally needed for RISC code generation. Since then, GRIN...

I added a brief description for the GADT-style AST, and the new datalog based model for the AST. The DL model will need named case alternatives.

Added a detailed explanation for named case alternatives.

I wrote a few lines about these in the as-pattern section.