But, if you assign an array to a new array, it doesn't quite work that way.
What's going on here? We made a change to
myScores changed too. Why would that happen?
As a metaphor, you can think of a number variable "holding" the number you assign to it, but an array variable "holding" directions to where to find the actual array.
So, when you assign
myNewNumber, what gets put in
myNewNumber is the value 42.
But, when you assign
myNewScores, what gets put into
myNewScores is a reference (the directions) to where the actual array is stored.
myNewScores are both pointing to the same place. Whichever one you access, your code is going to go to the same place to find the array.
So, if what you want is a copy of an array, and not just a copy of the directions to the array, you'll need to get the values out of the array and assign that to your new array. There are many ways you could do that.
One common way is to use
.slice() on the original array. With no arguments,
.slice() will return the whole array. A similar approach would also work with other array methods like
.reduce() as long as you set the method to return the whole array.
You can also use the
Array.from() static method which was introduced in ES2015 to create a new array from the old array and assign that.
Or, you can use array literal brackets and spread syntax
... to expand the old array into a new array and assign that.
These methods all result in "shallow" copies, which work fine for the simple arrays in these examples. But, if your original array contains nested arrays or objects, those sub-items in your new array would still be references (directions) to the original sub-items.
This idea of "by value" and "by reference" pops up in other areas too. Thinking of "by value" as "the thing" and "by reference" as "directions to the thing" is helpful to me to understand how that works.