Skip to content

Possibly change FSM from functional design to imperative design #49

Description

@r0liveir

Current design is implemented as:

def dispatch(state, event, actor) -> NewState:
 ....

Like a calculator. But execution in function seems ambiguous, with in-place modifications (although the state is returned later on). Perhaps we should change to imperative design, which may be better for this Event-Driven architecture

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions