Actions
Backport #5124
closed
foo = [*bar] implies foo.equal?(bar)
Description
I just ran into this as a result of some slightly sloppy coding, but it did disagree with my internal assumptions.
Normally, I expect the Array literal syntax to create a new object, every time. So when I rewrote some code and ended up with something similar to the following, my tests broke, and I'm not sure that's how it should be. Here's the reduced test case:
some_ary = [1, 2, 3]
bar = [*some_ary]
bar << 4
p bar
[1, 2, 3, 4]
p some_ary
[1, 2, 3, 4]
I see it's clearly taking an opportunity for optimization, so I'm more than happy to hear that as a reason for rejecting this. It does warrant documentation somewhere, though, I'd say. Not sure where that documentation would go.
Updated by 
Updated by 
Updated by 
Updated by
Actions