@Nick Smith To demonstrate the concept of “projectional syntax sugar” a bit more - here’s a simple example: The record below is equivalent to

{prev: num, next}

in JavaScript or

{prev = num, next}

in Haskell with

NamedFieldPuns

- the “next” field is set to the value of the variable with the same name -

I guess you could consider it the same thing as the "code folding" feature that many IDEs provide

To me folding feels different. It’s a mode of viewing and is maybe more related to turning type or value annotations on or off - it doesn’t affect the code but how you view it. In Lamdu if the code fits the pattern then it will always be displayed sugared. Caveat: the syntactical sugars are toggle-able in the configuration file and perhaps in a gamified tutorial in the future the sugars will be enabled one by one as you learn them. Btw some basic stuff like “if expressions” are just syntax sugar for pattern matching

Code folding only hides things whereas sugar does less trivial changes to how things are shown when they match a pattern, like the dual of macros

Sure, but it's the same principle: take the source code and display it slightly differently

However code folding tries to give you more choices while we try to reduce choices

What does "the dual of macros" mean?

@Drewverlee The choices code folding gives the reader is whether to view things expanded or collapsed