You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When encountering two syntactically-equal and type-equal Gen-initializations, apalache appears to cache the RHS, making it impossible to generate different values for two variables initializaed this way. For the attached module, apalache-mc check --length=0 results in a deadlock with --init=InitDeadlock, and no error with --init=InitNoDeadlock, even though the two Init- operators should behave exactly the same. The same bug occurs even if the types of a and b are more complex, e.g. Set({x: Int}).
When encountering two syntactically-equal and type-equal
Gen
-initializations, apalache appears to cache the RHS, making it impossible to generate different values for two variables initializaed this way. For the attached module,apalache-mc check --length=0
results in a deadlock with--init=InitDeadlock
, and no error with--init=InitNoDeadlock
, even though the twoInit-
operators should behave exactly the same. The same bug occurs even if the types ofa
andb
are more complex, e.g.Set({x: Int})
.The text was updated successfully, but these errors were encountered: