2:55 PM
i have a big brain idea for unparsable nilads
it has a bunch of unparseable nilads
now the program goes "hey i have a bunch of unparseable nilads at the end of the program"
then it converts those into a list like:
but then it sees an unparseable nilad
to be clear this happens before actual evaluation
now it keeps on eating nilads until it finds something else
next the same thing happens to finally become
now i don't know what to do in this case:
where unparseable nilads are surrounded by monads
@UnrelatedString @lyxal do y'all have any ideas?
so it basically stops 2,0 rule from occuring in cases like: +2 0 2+
but it evaluates this as 2,0 0,2 +2 2+