Loops

Connect output of a component to its own input and implement some update logic inside

Problems

TODO

UPD: not sure if this should be here

from neva.

Memory nodes

Introduce memory nodes that are like const nodes except they:

1. Have inports, not only outports
2. Only sends data after update from the inports

What must be decided is where memory gets default value. Possible options are:

1. It's part of the node's definition like in const
2. Default value is zero-value
3. Default value is zero-value but it's not used until first update arrived
4. There's no default value - first update used instead (assumes first update must contain full data)

Problems

• having one place for getting/updating message could lead to complicated schemas - in FBP assign component is used everywhere in the network where we want it to be used
• It's not clear should memory nodes really mutate memory or just create new messages
• How updates are implemented? Maybe separate issue needed
• Race conditions? TODO

Maybe related to #48 (maps and lists must also be thought of)

from neva.

Assign

TODO

from neva.

Use struct-builders (pair builders?)

The usecase is to mark objects to distinct them later. This could be done without modifications, just create wrappers. Same goes for case where we really need to update some field. Just create new struct

from neva.