neva
neva copied to clipboard
nevalang
🌊 Dataflow programming language with static types and implicit parallelism. Compiles to native code and Go
Having two packages is pointless since strconv and strings overlap and can be just merged into strings.
Only port should be used at a left side of the `-> (...)` connection. Constant messages are unconditionally sent in infinite loops by `New` emitter component. ```neva component Main(start) (stop)...
Turns out if you'll try to compare two `struct` (that are `map` under the hood in Go), there will be a panic. We need to implement this. However, it's not...
Current semantics is this - _at least one_ outports must be used. This has some problems. # Problem ## Unhandled Errors First of all errors could be unhandled. If component...
NodeJS added this in latest LTS release so I though it would be funny to have this too right in the stdlib. Could be separate package like `os/dotenv` or maybe...
```neva type User struct { age int name string } // FIXME - cannot use 'struct' as a node name component Main(start any) (stop any) { nodes { Println, builder...
``` [1, 2, 3] -> ... ["a", "b", "c"] -> ... [true, false] -> ... // ... {'foo': 42, 'bar': 420} -> // etc ... ```
1. What should we see in a console when we `panic`? In Go we see a stack-trace of the goroutine that panicked 2. Do we need something like Go's `debug.PrintStack()`...
We basically will have components that turn something that is not stream to a stream and vice versa. How should we name them? # Builtin Explicit (Option 1) ``` ListToStream...