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
ffsm should provide a fully exported functional API. This API could allow users to write and use state machines with function-call syntax instead of method-call.
The text was updated successfully, but these errors were encountered:
After thinking this one over, I feel like it's both not a worthwhile change and introduces some serious questions about maintainability.
Most notably, the only 2 ways I can think to persist a state machine while using a functional only API to mutate the state are to return a new state machine (creating an inconsistent API) or to keep track of the state machine in global memory, which I personally think will introduce serious headaches down the road.
As a result, I think this is best saved for an API change, perhaps as part of 0.2.0.
ffsm
should provide a fully exported functional API. This API could allow users to write and use state machines with function-call syntax instead of method-call.The text was updated successfully, but these errors were encountered: