[Quest] Execution order

[gregsn]

It's still not possible to express the execution order explicitly.

For descriptive patches (e.g. operating on immutable data) this is fine; especially when there is also no other side effect (write to disk & later on read back from that file)

But there are patches that come with

• imperative operation calls on mutable types
• side effects
• s & r nodes
  that need to ordered.

There are hacks, which work in certain cases:

This patch makes sure that CallingYouWhenInGoodMood and therefore SetData gets called before reading the Data back.

And that's the cleanest workaround I was able to come up with up to now. (I have seen worse workarounds that is) This situation clearly has to be resolved.

Note that the approach above only works if the part that I want to execute first (in this case the region) has an output that can be connected to the If-region. The hack is based on the idea that data-flow dependencies make the compiler execute the region before the Data node. Without the output on the region, this wouldn't be possible.

[gregsn]

All proposals should address Fragments of Process Nodes (as those are the to be order calls when talking about these kinds of nodes).

Those proposals are allowed to state: "It's not possible to order individual fragments with this proposal. You only can order all fragments of a process node with respect to other nodes." Or anything along these lines. But they should address the issue in some way.