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
Traditional finite state machines typically operate over a fixed input, nominally either a string or a vector of symbols. We should support that use case, ostensibly in the constructor, and/or with a .reset #449 , and/or with a direct call (the direct call is probably important for machines that need to be configured before run, but the constructor is probably the one that will mostly get used)
What this should actually do is take the inputs apart and issue them as a sequence of actions
"Bob" means machine.action('B').action('o').action('b');
input call
input as constructor arg
input wrt reset
The text was updated successfully, but these errors were encountered:
Traditional finite state machines typically operate over a fixed input, nominally either a string or a vector of symbols. We should support that use case, ostensibly in the constructor, and/or with a .reset #449 , and/or with a direct call (the direct call is probably important for machines that need to be configured before run, but the constructor is probably the one that will mostly get used)
What this should actually do is take the inputs apart and issue them as a sequence of actions
"Bob"
meansmachine.action('B').action('o').action('b');
The text was updated successfully, but these errors were encountered: