When the Next Step Is Not One Step: Distribution-Aware Execution Modeling for Concurrent Go Programs (opens in new tab)

Training a model to predict the next step in a concurrent program is harder than it looks: two runs of the same program from the same trace prefix can produce different next events, both valid, because the scheduler is nondeterministic. A model trained against a single label is learning to guess one outcome of a random process. We turn this around and use the nondeterminism as a training signal. We run each program many times, aggregate the obse...