> At any instant, the program state is completely described by the code you see.
I think that is generally not true in Pluto. Citing from <https://github.com/fonsp/Pluto.jl/issues/316>: # Example (each row in a separate Pluto cell): a = [4, 3, 2, 1] a # prints [4, 3, 2, 1] sort!(a) # prints [1, 2, 3, 4], but does not update previous cell Run And I believe that if instead of `sort!` you used something like `append_zero!` (which does in-place modification of the given vector and appends number 0 to it) then `a`'s value would depend on the number of evaluations of `append_zero!(a)`.
