Get rid of bypass

Use arr ports only by referencing them

Problems

• #29

UPD: For now it looks like array-bypass may not be needed. What if array ports may be used only with indexes? But at the same time it makes them not flexible...

UPD: For now it looks like array-bypass needed because of reasons described in the issue

from neva.

Allow bypass for only network's inports

If module has array inport then it must use bypass connection. If module uses sub-component with array-inport it must not use bypass and use indexing instead. This way there will always be place in the program where array-inport used by indexes.

Problems

It wont work. If sub-node's array-port elements must be used by referencing them then it's impossible to do anything with bypass. Unless we have some special Indexer component with err outport for handling indexing errors (which is bad because array-ports considered to be a static data (tell this to operators))

from neva.

Compute first parent that uses indexes

If array-inport used by bypass-connection inside the module's network then look at how it is used by parent network:

• If parent network uses it with indexes then use those indexes (base case)
• If parent network uses bypass too, then:
  • If parent's bypass comes from the parent's inport go to 1
  • If parent's bypass comes parent's sub-node
    • If subnode is

TODO

from neva.

Allow bypass from inports to nodes but not from nodes to nodes

Fix of #41 (comment)

If module has array inport then it must use bypass and it's allowed to pass it further to sub-node. But if module uses sub-node with array-outports it must use them via indexes.

TODO think more

Problems

• Need for err-like outport for all such components?

from neva.