Feature request: move semantics for flow graph outputs
I'd like to request adding the ability to send and receive types which are not copy constructible in a flow graph.
Obviously this makes sense only if there is exactly one edge coming from the output port to one input port.
Given the input/output ports are set at compile time, it seems possble to have a specialization for non copy constructible types that throws an exception if more than one edge is created from an output port for such a type.
Sometimes it is desirable to have a heavy object live entirely within the flow graph. One can use a shared_ptr, however that is not always compatible with the existing architecture.
@aleksei-fedotov is this still relevant?
@aleksei-fedotov is this still relevant?
I would say yes as I cannot remember the work on this enhancement had been considered, but I may be wrong here. It is better ask people who recently worked with the flow graph code. @kboyarinov, @pavelkumbrasev