Guess at a place where checking of termination conditions should occur
This commit is contained in:
parent
aae15a008b
commit
bddcf9a240
|
@ -74,9 +74,11 @@ This is leading me to believe that the order of operations is:
|
||||||
- update `track`s and assertion-sets related to `rising-edge`.
|
- update `track`s and assertion-sets related to `rising-edge`.
|
||||||
- handle `on` for `asserted`, `retracted` and `rising-edge`, in order of appearance (!?)
|
- handle `on` for `asserted`, `retracted` and `rising-edge`, in order of appearance (!?)
|
||||||
- maintain `assert`s
|
- maintain `assert`s
|
||||||
|
- check termination conditions
|
||||||
- Given a message,
|
- Given a message,
|
||||||
- handle `on` for `message` and `rising-edge`, in order of appearance (!?)
|
- handle `on` for `message` and `rising-edge`, in order of appearance (!?)
|
||||||
- maintain `assert`s
|
- maintain `assert`s
|
||||||
|
- check termination conditions
|
||||||
|
|
||||||
Actually, I'm not sure `falling-edge` is encodable using
|
Actually, I'm not sure `falling-edge` is encodable using
|
||||||
`rising-edge`, since the initial state might be different. Do we
|
`rising-edge`, since the initial state might be different. Do we
|
||||||
|
|
Loading…
Reference in New Issue