Strange closure behaviour

[Emmanuelle]

On Saturday, 15 June 2019 at 16:29:29 UTC, Rémy Mouëza wrote:
> I don't know if we can tell this is a compiler bug. The same 
> behavior happens in Python. The logic being variable `x` is 
> captured by the closure. That closure's context will contain a 
> pointer/reference to x. Whenever x is updated outside of the 
> closure, the context still points to the modified x. Hence the 
> seemingly strange behavior.

I come from Ruby, where it works as I expected, so I assumed all 
languages would work like that; but then, D surprised me, and 
now, Python too, and apparently a whole bunch of other languages 
(which is honestly kinda disheartening since I like throwing 
lambdas everywhere.)