Open no-reply opened 8 years ago
This is failing on Rubinius 3.29 in CI. I can't repeat the failure with 3.30 At a glance, this looks like a bug in 3.29.
I can't install 3.29 locally due to LLVM incompatibilities; but might be able to look into it another time. We should evaluate this more thoroughly before moving forward.
Personally, I don't care if tests fail on Rubinius. Rubinius is a buggy heap of... bugs.
Sorry, what was the motivation for the removal of all occurrences of &block
?
This is a follow-up to #189. The Ruby core issue that gave rise to that ticket has been patched since last August. It's probably still worth discussing whether any releases missing the patches should be supported.
In addition to reverting the original patch for #189., this aims to remove unneeded
&block
parameters throughout.My benchmark results on
bench/hash/each_bench.rb
are too variable to say anything too conclusive. Still, I modified the file withb.warmup = 10; b.time = 60
, and here are my results. They, at least, point to this making a measurable difference: