We have some ideas for how to make nevalang programs more readable with #719 #721 and #722 but that's not everything that programming language usually helps with through interface of so called "operators". These are left:
We don't talk here about for look (we have ForEach HoC but #711 and it's not that powerful on context of scope capturing (we don't have closures))
Existing syntax (including deferred and chained connections as well as fan-in and fan-out) makes dataflow clear. Don't we damage dataflow readability by adding control-flow-ish (visually of course) statements? Is it still clear that instructions are not executed "from top to bottom" or the dataflow itself (where data comes from, how are connections formed)?
We have some ideas for how to make nevalang programs more readable with #719 #721 and #722 but that's not everything that programming language usually helps with through interface of so called "operators". These are left:
Routers:
Selectors: