From: Greg.mpls@... Date: 2018-12-28T23:30:28+00:00 Subject: [ruby-core:90782] [Ruby trunk Bug#15479] Array#reject! modifies literal Array Issue #15479 has been updated by MSP-Greg (Greg L). Is the distinction really whether 2.6.0 & trunk only modify the array if `reject!` successfully enumerates all array members? Commenting out `when 3 then raise StandardError, 'Oops'`, all versions act the same... ---------------------------------------- Bug #15479: Array#reject! modifies literal Array https://bugs.ruby-lang.org/issues/15479#change-75955 * Author: Eregon (Benoit Daloze) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.6.0p0 (2018-12-25 revision 66547) [x86_64-linux] * Backport: 2.4: DONTNEED, 2.5: DONTNEED, 2.6: REQUIRED ---------------------------------------- This was found by running ruby/spec with -R2 (such as mspec -R2 -fs core/array/reject_spec.rb). TravisCI log on https://travis-ci.org/ruby/spec/jobs/473175799#L539 Here is a simple reproducer. MRI seems to modify the Array literal permanently: ```ruby 3.times do a = [1, 2, 3, 4] puts "initial: #{a}" begin a.reject! do |x| case x when 2 then true when 3 then raise StandardError, 'Oops' else false end end rescue StandardError end puts "after: #{a}" end ``` prints ``` initial: [1, 2, 3, 4] after: [1, 3, 4] initial: [1, 3, 4, 4] after: [1, 3, 4, 4] initial: [1, 3, 4, 4] after: [1, 3, 4, 4] ``` 2.5.3 behaves fine, but trunk is also affected. -- https://bugs.ruby-lang.org/ Unsubscribe: