Fork me on GitHub
#architecture
<
2018-02-21
>
drewverlee04:02:56

Contrasting that with another lib: https://github.com/cdorrat/reduce-fsm Which seems to make returning to states a bit more explicit (not sure if thats better or worse).

Ivan09:02:01

@drewverlee you never "return" to "previous" states

Ivan09:02:24

you at state 'x' and the allowed transitions are 'y' and 'z'

Ivan09:02:41

if you are in a cycle, there is no ordering

Ivan09:02:46

you always move forward

Ivan09:02:30

the only exceptions are the entry point and the end/final state

drewverlee13:02:56

@ivan.kanak_clojurians maybe i’m using the wrong terminology, if you look at the graph above i’m not sure how else to describe :error taking someone to 0. I think its probably correct to say its not the same ‘state’.

Ivan13:02:26

Going from (2) to (0) is a move forward, even if it feels like (0) is "before" (1). It is not "before", but a prerequisite state to get to (1). You never go backwards, you never take back the fact that you got to (2) through (1). You are always progressing, and the progressions happen by choosing one of the available/valid transitions. Following the transitions you always move forward.

john15:02:05

Pushdown automata have local state you can bang on, sorta