Open bugarela opened 1 month ago
This seems to be also happening when calling setBy
with a non-existent key
Also about setBy: sometimes it properly reports an error, but it seems like it finishes the entire simulation to only then report it. So you wait for nothing.
Changing the trace.result/outcome from Maybe to Either should help identify the problem(s) here.
A similar problem: the simulator crashes when running with an invariant that does not exist (ie, mistyping the name)
If the init action refers to vars, the simulator breaks. Instead, we should properly report/explain the error.
MWE:
Results in: