making good progress on my parser, and now i'm thinking of committing some crimes >:3

that being having both `and` and `&&`, and `or` and `||`, where the latter coerces to bool and the former does not and acts like lua >_>

#PLDev

in less trolling news i'm really liking the way if/while/etc blocks work in this syntax. either you do this

if x { ... }

or you do

if x: print "single line";

so the colon delineates the end of the condition but is optional if you have a {} block instead of a single line. and yes, this is also valid:

if x: { ... }

not sure what i wanna do with for loops 🙃 C style for (;;) or Lua style for x = 1, 10

@eniko yall got lambdas?

```for_each (sequence, ^ (item) {
work (item);
});

for_each_n (sequence, ^ (item, i) {
work (item);
array[i];
});```

etc

then later you could do what Ruby/early Rust did and allow the recursion-operators to curry and implicitly use trailing-call syntax:

for_each (sequence) ^(item) {
work (item);
};

(i am hung up on this :P)

@erisceleste nope, too fancy for me
@eniko i poisoned my brain with Lisp at an early age and am now unable to think of the C-style control structures as anything other than higher-order functions that curry with a lazy condition-expression and are then invoked with a block-lambda
@erisceleste @eniko I managed to avoid the Lisp indoctrination, but instead got sucked int Forth at an early age. Now everything is about popping stuff on and off stacks.

@pzmyers @erisceleste @eniko

parents, talk to your children about programming languages before it's too late 😂