[erlang-questions] Why single-assignment with non-shared state?
Sat Oct 20 13:33:46 CEST 2007
While single assignment and pattern matching go very well
together, it's a little bit less obvious how mutable state and
pattern matching would combine as nicely. Erlang's current
semantics for binding and matching make it quite straight-
forward to reason about even very complex programming
2007/10/20, Tobias Gerdin <tobias.gerdin@REDACTED>:
> Hi there,
> I do not understand why the single-assignment restriction exists in
> Erlang (even though I very much enjoy functional programming) given
> that processes do not share state. What is the problem with mutable
> state in a concurrent system when other processes cannot access other
> processes' state?
> I was hoping someone could enlighten me on this matter.
> erlang-questions mailing list
More information about the erlang-questions