Can one of you explain to me what is going on here and how to avoid it? Can you reproduce this behaviour? When I define x as x = zeros(10) x .= .05 x I get Vector{Float64} with 10 elements 0.0500 0.0500 0.0500 0.0500 0.0500 0.0500 0.0500 0.0500 0.0500 0.0500 when I assign x to y: y = x x I s…

Julia like most other high level languages (oppose C) think of variables as pointers to data. Thus y=x doesn’t mean “make y hold a copy of x”, but instead means “make y a synonym for x”. Thus changing y, naturally, changes x. If you want a copy, you should instead write y=copy(x).

Why is Julia messing up my variables?

New to Julia

Juan January 16, 2020, 4:28pm 9

But then why would you need to make b = a and not just keep using a?

Topic		Replies	Views
Copy vector? New to Julia	5	7051	April 7, 2019
Assignment of array elements New to Julia question	2	5292	February 1, 2018
Why making a change in a copy of a variable changes the original variable? New to Julia	16	4461	November 14, 2020
Copying subvector makes pointer? New to Julia	5	376	March 11, 2021
Matrix values New to Julia question	9	685	October 7, 2020

Why is Julia messing up my variables?

Related topics