Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
,Used in:
The actual arguments to a function/method call. For example, in `foo(4, 5)`, `4` and `5` are arguments.
Used in:
,Used in:
, , , , , , ,Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Counter defines the metric to be collected. This can be used to collect the number of times a branch is taken. Or other cost metrics like resource usage, or price. This is equivalent to reward in PRISM. For now, supports only simple numberic values. Eventually, this should support distributions like normal, exponential, etc.
Used in:
The value to be added to the counter.
Used in:
Used in:
, , , , , , ,Used in:
,Used in:
StateVars variables = 5; Action init = 5;
Used in:
, , , , , ,Used in:
Used in:
Used in:
,Used in:
Used in:
Used in:
,Used in:
Used in:
Used in:
Used in:
If true (default), model checker would evaluate the possibility of a crash at yield points.
Variables in the function/method declaration. For example, in `def foo(x, y)`, `x` and `y` are parameters.
Used in:
,Used in:
int32 offset = 1;
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
, , , , , , , , , , , , , , , , , , , , , , , , , ,Set options like max_actions for individual action instead.
If true, continue exploring the state space of other paths that did not fail.
If true, continue the failed path as well, ignoring the invariant failure. This is almost equivalent to not having the invariant at all, but it can be useful for debugging
Default is 'strict' implies liveness check is done TLA+, the other options are 'probabilistic' The probabilisitic model checker is not integrated into the playground but has to be run separately in commandline.
Enable (default/true) or disable deadlock detection Note: explicitly setting it optional, makes this tristate
Used in:
,Used in:
, ,Used in:
The probability for the branch to be taken.
Used in: