At present, the stack trace shows all the sources of non-determinism, including those without a yield point. In majority of the scenarios, these rows are not useful, except for the actual choices (link names) made.
We can't remove it completely, as there are some scenario's this will be crucial.
- the
any statement happens deep within the execution of certain steps.
- the
any statement is executed within a loop.
any statement after yield points. For actions that are not atomic, where there can be multiple thread interleavings, this will get more complicated.- for probability/performance modeling as having this is required to set the correct probability.
At present, the stack trace shows all the sources of non-determinism, including those without a yield point. In majority of the scenarios, these rows are not useful, except for the actual choices (link names) made.
We can't remove it completely, as there are some scenario's this will be crucial.
anystatement happens deep within the execution of certain steps.anystatement is executed within a loop.anystatement after yield points. For actions that are not atomic, where there can be multiple thread interleavings, this will get more complicated.