From: ismaelga@...
Date: 2015-01-20T22:51:04+00:00
Subject: [ruby-core:67709] [ruby-trunk - Misc #10754] Tiny optimisation of	Set#include?

Issue #10754 has been updated by Ismael Abreu.


With the benchmarks I've run I noticed that ~~sometimes~~ rarely, the old include? was faster.
Do you have any idea why is that? The only cause I can think of is the GC.

----------------------------------------
Misc #10754: Tiny optimisation of Set#include?
https://bugs.ruby-lang.org/issues/10754#change-51141

* Author: Ismael Abreu
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Hi!

I'm not sure if this a relevant optimisation but here it goes. A simple way to improve Set#include?
I don't think there should be any side effects with this change.

Here are some dummy benchmarks https://gist.github.com/ismaelga/68bb3ea51b4742f65699
They are not consistent, but that should be because of garbage collection or something. Right?

I've also sent a Pull Request: https://github.com/ruby/ruby/pull/810

---Files--------------------------------
patch.diff (544 Bytes)


-- 
https://bugs.ruby-lang.org/