4 ms·
"The overwhelming majority of programmers have only used languages with multiple assignment. Multiple assignment is the de facto standard, and single assignmen
by jamesbritt 18y ago
"The overwhelming majority of programmers have only used languages with multiple assignment. Multiple assignment is the de facto standard, and single assignment is one of the things that makes Erlang weird to new programmers. "
So what? "But it feels weird!" is not an argument. It is an excuse.
It's like when people dismiss Lisp because of all those parentheses; you get over it, and eventually find more interesting things to focus on.
- qwph 18y agoAlthough some people, when faced with a problem they don't understand, will just give up and do something else instead. Admittedly, I don't have any metrics on how many people have abandoned Erlang because of single assignment, or Lisp because of the parentheses, but I'm sure such people exist. And you might say that it's their loss, and I'd probably agree with you.
- jamesbritt 18y ago"And you might say that it's their loss, and I'd probably agree with you." Indeed I would say that. But there's another side. When a language allows for slippage in conceptual integrity for the sake of familiarity, everyone loses. For example, I'm a big fan of Ruby, but there a number of places where consistency in language axioms was dropped so as to supposedly make it more intuitive. It does so at the cost of everyone having to remember both the fundamental concepts (e.g., "the last expression evaluated in a method is the return value") and the exceptions ("except when the method name ends with '='). Lazy people like me think that's just extra work. :) I don't know Erlang, but I suspect that if some form of "multiple assignment that isn't really the multiple assignment you're used to" were allowed, people would still have problems with it, but they would be harder to understand and resolve based on core language principals.
- jlouis 18y agoYour last paragraph show you have the right hunch. Erlang has a pretty simple binding compared to, say, ML. In the statement X = Expr, Body Evaluates Expr, binds it to X and evaluates the body with X bound. This is akin to variants of let-bindings found in so many other languages. The difference is, however, that the binding can not be shadowed. If body contains, say: X = Expr2, it is taken as an assertion: Evaluate Expr2 and compare it to X, crashing the program if Expr2 is not equal to (in effect) Expr. What some miss is that this is not mutation, but binding. In X = 0, F = fun (Y) -> Y + X end, X = 1, F(4). The X inside the body of F is bound to 0 and not 1 when F gets evaluated because any semantics apart from this would be silly in a functional language with lexical scope. And since Erlang has no concept of Let-bound scopes in functions it would probably give some of the problems you mention. I guess the Prolog-history plays a part in the decision, but also the fact that explicit (single) assignment is a really good tool for weeding out bugs: Any use will explicitly refer to exactly one def. Several compilers that allow shadowing of let-scopes even go as far as including a warning when you shadow variables!
- davidw 18y ago> And you might say that it's their loss, and I'd probably agree with you. Enough people give up, though, and it's your loss as a user of that language. Say out of every 100 people that give up, 1 is someone who is capable of contributing something good back, and 10 are people who might have answered questions on mailing lists or IRC, or written some blog entries or something. Languages do have network effects.
- jamesbritt 18y agoSure, but it's hard to say if adding or omitting a feature is going to be a net win for a growing user base. All things being equal, I'd rather a somewhat smaller user base for a language that is more easily internalized than a larger user base where you really do need the extra help to understand all the quirks of a language. Were that language design so simple ...
- davidw 18y ago> Sure, but it's hard to say if adding or omitting a feature is going to be a net win for a growing user base. I meant more along the lines of libraries to do useful things, which is a win pretty much any way you look at it.
- smanek 18y agoBut, it seems like it should be relatively simple to make the compiler convert your multiple assignment code to static single assignment form at compile time, with relatively little trouble. If there is any good reason not to do this, or if it is impossible/difficult, then I would understand single assignment. I just think the reason for it needs to be explained. Similarly, if single assignments aims to satisfy a different set of tradeoffs, and somehow grants some advantage that multiple assignment does not, it seems like these should be clear enumerated. In Lisp, for example, when new programmers complain about the parens, we usually explain that the they allows code to be equivalent to data and make the code directly be a parse tree. Which, among other advantages, makes macros far easier and cleaner. I haven't seen any similar advantage expressed other than some hand waving about concurrency. If single assignment makes concurrency easier, how does it do so?
- LogicHoleFlaw 18y agoThe reasoning that appeals to me most about single-assignment is the idea that it makes it easier to reason about what actions could have altered the state upon which the currently considered code operates. It makes explicit which code branches a particular expression is dependent upon. Supposedly this simplifies refactoring and reasoning about code. This justification sidesteps the idea of facilitating concurrency. It's similiar to the reasoning behind pure functional approaches where side-effects are avoided. I've personally worked with code where single-assignment would have avoided bugs which were introduced because later modifications did not completely account for previous possibly state-altering actions. On the other hand this article shows places where enforcing single-assignment on the programmer makes reasoning yet more complicated. I'm not completely sure what my final opinion on the subject is. Side effects, state, and assignment can all be considered orthogonally and I'm not sure what the best way is to deal with them. Maybe Haskell has the answer with its Monads, but I haven't examined the language closely yet. One thing I liked about Pascal is the difference between the := (assignment) and = (equality) operators. You also had Procedures with side effects and Functions without. Separating these concepts definitely added to the pedagogical utility of the language. As I learn more about these concepts I find myself more explicitly managing assignment, state, and side-effects in my code. Even in imperative or OO workaday languages such as PHP or Java. I will attest that it does make a difference in the ease with which I can decouple and maintain an ordinary codebase.
- michaelneale 18y agoInterestingly scala makes the choice fairly explicit - val or var - your choice. In practice I find I default to using val - as I know when I debug I only have one place to look for where the value is, and there is generally less cursing when a value mysteriously changes (it doesn't). (Java has final, and C# has 'const' which is kinda similar). Although in their case you have to choose extra verbosity, but its often worth it.