dumblob

Stay on the floor, don't generalize and explain your feelings a little bit deeper and you might get some plus points for `for (...)` from me, but I don't guarantee...

`do-while` is redundant, I just too boringly agree ;) as I wrote earlier. But introducing another additional redundant syntax sugar for an infinite loop, which is even longer to type...

It's also interesting, that there are already more issues somehow related to tuples :wink:: https://github.com/daokoder/dao/issues/355 https://github.com/daokoder/dao/issues/433 https://github.com/daokoder/dao/issues/438 https://github.com/daokoder/dao/issues/472 https://github.com/daokoder/dao/issues/430

I'd also expect casting working over newlines: ``` 0$ cat ~/del/a.dao { (tuple) ('a', 'b'), }.iterate { io.writeln(X) } 0$ dao ~/del/a.dao ( "a", "b" ) 0$ cat ~/del/b.dao {...

And there is mismatch in reporting an issue in code sections: ``` 0$ cat syntax_err.dao { (a="sth0", b=7), (a="sth1", b=8), }.iterate { # ... whatever code here io.writeln( 'abc' +...

The first issue `type T = tuple; {(T)(0, 1), (3, 2)}.iterate{io.writeln(X)}` is already solved and seems to work. The other two issues persist :wink:.

Sounds feasible.

`io.put` would resemble byte-wise output as well, so I'd prefer `io.print` or similar.

Our policy is to accept backends despite them being incomplete or buggy or whatnot. Just document the downsides and we'll merge it :wink:. We appreciate the effort. Thanks a lot!

I'm out of time now to look at the code, but just want to mention that in my opinion the "Nuklear style" is probably less interesting than the C++ ->...