neva
neva copied to clipboard
🌊 Flow-based programming language with static types and implicit parallelism. Compiles to native code and Go
FP and related components that will work together. Please add comments and suggestions inline.
In a structural type system I should expect to use `Match` to do this: ``` ... -> match:data // pass stream to data {last: true} -> match:case[0] -> :stop ```...
Because runtime implements sort-of pub-sub algorithm based on spawning a goroutine per connection where connection is one sender -> multiple receivers. If we have e.g. 2 connections with the same...
In control flow languages we have concept of _scope_ ```python3 a = foo() b = bar() baz(a) ``` The reason for that is that in a control-flow language you describe...
# Change Existing Syntax (Sender Side) ## Before ```neva foo:bar.baz.bax -> ... ``` ## After ```neva foo:bar -> .baz.bax -> ... ``` ## Implementation Details 1. Remove `selectors` from `SenderSide`...
It's not clear and should be fixed somehow
We need to look at - https://axios-http.com/docs/intro - https://pypi.org/project/requests/ - https://pkg.go.dev/net/http And implement more components in `http` package, at least we need to be able to - Send `POST` requests...
Sometimes we need order not depending on actual timing of events but rather on a topology
Almost same as #647 but simpler, instead of `res T` it produces `res bool`
Almost same as #289 except 1. Emits single elements instead of stream(s) 2. Emits result as soon as first element found and skips other elements # API ```neva pub interface...