What’s the difference between variable binding and assignment? How does that work on a low level?

As I understand it (read it with scepticism), in case of Elixir: binding would be an expression, assignment is statement. In Elixir = is basically a pattern matching with binding(?) Since BEAM has only immutable values, binding making much more sense. Maybe I’m simplifying a lot - assignment assig…

A couple clarifications: There is no “assignment” in Elixir[1], when you use ‘=’ you are doing a pattern match and it either succeeds or fails. If it fails, the current process crashes. The compiler/runtime has a set of rules that it uses to attempt to make the pattern match succeed. One of these …

[image] bbense: [2]- If I am understanding it correctly: Under the hood the Elixir compiler actually creates a new variable name and just remembers that x is really x1 from now on. That is precisely correct, though the name is a bit different, but yep. :slight_smile: You can see the Erlan…

Great question :023: I’ve also wondered the same thing. So would it be safe to say the following? Binding has to do with giving names to things (or values) in a given well delimited context. Assignment is about storing things (or values) in some location (a variable) From: https://cs.stackexch…

[image] AstonJ: So would it be safe to say the following? Seems pretty good. :slight_smile: I’d think the most ‘pure’ way of thinking of bindings are as unevaluated closures, so even doing just a = 4 means define a 0-arity function a in the current scope with the running environment that ju…

Is there any problem in code like this? var1 = 123 var1 = get_new_value(var1, :something) var1 = get_new_value2(var1, :something2)

The code you showed works. However, we usually try to reduce the number of single use variables. So, the “Elixir way” of writing that code is var1 = 123 |> get_new_value(:something) |> get_new_value(:something2) Furthermore, if it was the last statement in a function, then we would drop the…

[image] nezzart: Is there any problem in code like this? The other issue with rebinding is that the name var1 may not only be bound to a new value but that the value could be an entirely different type. var1 = 123 # this is an integer var1 = get_new_value(var1, :something) # this could be a …

I’m not asking how to simplify that. moreover, how’s that diffrent from? def my_fun do # ... get_new_value(123, :something) |> get_new_value(:something2) end

my question was about multithreading safety and related stuff.

What's the difference between variable binding and assignment?

Questions & Help Questions

nezzart May 14, 2017, 5:00am 16

get_new_value(get_new_value(123, :something), :something2)

that’s it.