-
First idea was to have `Main (start T) (exit int)` but then in turns out that using of type-parameters makes no sense there because there's only one use-case always - runtime sends `nil` (or maybe som…
-
Isn't these the same thing?
- unbox field `a` from outport `v` like `v.a`
- route that `v.a` to `c1` downstream node and unbox it `v.a.x` on the input side
- also route `v.a` to `c2` but unbox `v…
-
We use triggers to implement static inports. Why don't we use components to implement record fields and array elements reading? It would simplify program structure.
The problem is in langs like go…
-
In "Dataflow and reactive programming" book IIPS (initial values/tokens) described as things that are sent only once. This is not how this work in Nevalang.
1. Find out how this works in FBP
2. Fi…
-
Looks like data split is forbidden in classical FBP (check this out in book or at least ask chat-GPT). In the "dataflow and reactive programming" book there's a section about features combination in d…
-
The text is in Russian because I just wanna leave it here so it won't lost. It's easy to translate it to English if needed.
I was adding desugarer component to the compiler so user can use not all …
-
It's impossible to create component dynamically at this point. The program structure is is static. There are specific cases of this problem like:
1) Makes impossible to program to modify itself (me…
-
> I though this #29 was closed but turns out it's not.
There are cases (e.g. router) where array-outports must be used by indexes. On the other hand it's not safe - if I use `arrOut[2]` there's no …
-
This issue describes 4 problems with current design of static messages
1. There's no way to use `selectors` with static messages right now
2. Keeping them in `nodes` leads to a special case (there…