fptools.state¶
Pythonic FP - State Monad
Handling state functionally.
##### class State - Classic FP State Monad
A pure FP immutable implementation for the State Monad.
translated to Python from the book “Functional Programming in Scala”
authors Chiusana & Bjarnason
run “action” returns a tuple
(a, s)
reversed to the typeState[S, A]
the standard convention seen in the FP community
another “factoid” to remember
choose the name
bind
instead offlatmap
the
flatmap
name is misleading for non-container-like monadsflatmap
name too long,bind
shorter to typewithout “do-notation”, code tends to march to the right
typing for the
modify
class method may be a bit suspect
- class pythonic_fp.fptools.state.State(run: Callable[[S], tuple[A, S]])¶
Data structure generating values while propagating changes of state.
class
State
represents neither a state nor (value, state) pairit wraps a transformation old_state -> (value, new_state)
the
run
method is this wrapped transformationbind
is just state propagating function composition
- bind(g: Callable[[A], State[S, B]]) State[S, B] ¶
Perform function composition while propagating state.
- eval(init: S) A ¶
Evaluate the Monad via passing an initial state.
- static get() State ¶
Set run action to return the current state
the current state is propagated unchanged
current value now set to current state
will need type annotation
- map2(sb: State[S, B], f: Callable[[A, B], C]) State[S, C] ¶
Map a function of two variables over two state actions.
- static modify(f: Callable[[ST], ST]) State[ST, tuple[()]] ¶
Modify previous state.
like put, but modify previous state via
f
will need type annotation
mypy has no “a priori” way to know what ST is
- static put(s: ST) State[ST, tuple[()]] ¶
Manually insert a state.
THe run action.
ignores previous state and swaps in a new state
assigns a canonically meaningless value to current value