Quim Muntal

@aarzilli @derekparker I'm mostly done with this PR and all tests in `pkg/proc` are passing. Could you do one final review? About the Windows ARM64 builder, anyone can register for...

Thanks for reporting this issue. The API is still not closed, and it won't be until there is a `v1` release, so I would rather fix the inconsistency now.

The README can't contain all the definitions, else it would become unreadable. Please take a look at the runnable examples in https://github.com/qmuntal/stateless/blob/master/example_test.go, there you have everything you need (I hope).

Thanks for the detailed proposal @stevenferrer. Passing down the arguments from `FireCtx` to the state mutator/accessor function is feasible, even without breaking existing API. We could have another state machine...

Can you specify why you need the arguments in the `Transition`? They are normally already passed in the function call-backs.

I'm hesitant to add the `Arguments` property to `Transition`. It does make sense but there are already many callbacks whose parameters are a transition and the arguments, so it would...

Hi @luxl, there is no way to set a general trigger for all the states, so will have to do it one by one when defining the state machine. Anyway,...

Hi @avixFF, internal transitions are standard state machine concepts, nothing specific to this library. From wikipedia: > Very commonly, an event causes only some internal actions to execute but does...

> internal transitions is basically a way to define multiple independent events with different logic for the same state? Yep, and those events don't trigger any state transition.

I've been playing with type parameters since the beginning, but I'm still not sure if they are a good addition to this library. Anyway, you can try them by pointing...