Node Inputs are only allowed one connection. I'd argue that one should be able to define how many connections are allowed for a Node Input, i.e negative number for infinite and a positive number for constrained, which can be defaulted to 1.
I did notice that in ryvencore the graph_adj_rev relates one input to a single output, which means this implementation is ryvencore specific as well. I could look into the refactoring needed for this to work, but first I want to know:
Is there a reason that an input takes only one output? Would data be lost otherwise? I can see how the design of connecting and the nodes updating on connection would favor ryven, but it probably limits ryvencore.
Is this tightly coupled with the whole system, or could it be easy to change? I don't have a lot of time to spend on this, so an estimation on how much things might break will help me.
I hope I am right in saying that an input updating from a number of outputs can make sense.
Node Inputs are only allowed one connection. I'd argue that one should be able to define how many connections are allowed for a Node Input, i.e negative number for infinite and a positive number for constrained, which can be defaulted to 1.
I did notice that in ryvencore the
graph_adj_revrelates one input to a single output, which means this implementation is ryvencore specific as well. I could look into the refactoring needed for this to work, but first I want to know:I hope I am right in saying that an input updating from a number of outputs can make sense.