Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tape Input #450

Open
3 tasks
StoneCypher opened this issue Feb 9, 2020 · 0 comments
Open
3 tasks

Tape Input #450

StoneCypher opened this issue Feb 9, 2020 · 0 comments

Comments

@StoneCypher
Copy link
Owner

StoneCypher commented Feb 9, 2020

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment