Actions
Bug #5752
closedArray#delete_if side effects due to changeset r32360
Description
It seems that the changeset r32360 introduced another side effect. Here are two IRB sessions, one in ruby-1.9.2-p136 and the other in ruby-1.9.3-p0:
ruby-1.9.2-p136 :001 > x = [1,2,3,4,5,6,7,8,9]
=> [1, 2, 3, 4, 5, 6, 7, 8, 9]
ruby-1.9.2-p136 :002 > x.delete_if {|i| i == x[i-1]}
=> []
ruby-1.9.3-p0 :001 > x = [1,2,3,4,5,6,7,8,9]
=> [1, 2, 3, 4, 5, 6, 7, 8, 9]
ruby-1.9.3-p0 :002 > x.delete_if {|i| i == x[i-1]}
=> [2, 3, 4, 5, 6, 7, 8, 9]
If this is indeed the intended behaviour, it should probably be documented clearly that the array is changed instantly every time the block is called and not after the iteration is over.
Files
Updated by funny_falcon (Yura Sokolov) almost 13 years ago
Actually, it were next changeset r32373
Updated by funny_falcon (Yura Sokolov) almost 13 years ago
- File array.c.patch array.c.patch added
Updated by nobu (Nobuyoshi Nakada) almost 13 years ago
- Category changed from core to doc
- Status changed from Open to Closed
Updated by akr (Akira Tanaka) almost 10 years ago
- Related to Feature #10714: Array#reject! nonlinear performance problem added
Actions
Like0
Like0Like0Like0Like0