[erlang-questions] Why single-assignment with non-shared state?

Tobias Gerdin <>
Sat Oct 20 11:50:14 CEST 2007

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.



More information about the erlang-questions mailing list