Open
Conversation
Reverts the change motivated by https://bugs.ruby-lang.org/issues/11451, see also hamstergem#189. The underlying issue was fixed in r52717, which is in Ruby 2.2.5. This requires some discussion about whether support for earlier Ruby 2.2.x releases can be dropped at this stage.
Author
|
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. |
Contributor
|
Personally, I don't care if tests fail on Rubinius. Rubinius is a buggy heap of... bugs. |
Contributor
|
Sorry, what was the motivation for the removal of all occurrences of |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
&blockparameters throughout.My benchmark results on
bench/hash/each_bench.rbare 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: