[#18121] [Ruby 1.8.7 - Bug #405] (Open) ssl.rb:31: [BUG] Bus Error — Anonymous <redmine@...>

Issue #405 has been reported by Anonymous.

14 messages 2008/08/04

[#18130] Re: New array methods cycle, choice, shuffle (plus bug in cycle) — Brian Candler <B.Candler@...>

> Seriously though... Array.first is a noun.

10 messages 2008/08/05

[#18319] NEW Command: absolute_path() -- — "C.E. Thornton" <admin@...>

Core,

14 messages 2008/08/16
[#18321] Re: NEW Command: absolute_path() -- — Yukihiro Matsumoto <matz@...> 2008/08/18

Hi,

[#18381] [Bug #496] DRb.start_service(nil) is very slow — Hongli Lai <redmine@...>

Bug #496: DRb.start_service(nil) is very slow

11 messages 2008/08/25

[ruby-core:18076] Equality of recursive arrays

From: "Vladimir Sizikov" <vsizikov@...>
Date: 2008-08-02 00:02:16 UTC
List: ruby-core #18076
Hi,

I'm currently writing RubySpecs for all Array methods with recursive
arrays, and I noticed something that I'd like to double-check with
you.

Essentially, the equality is not working right for recursive arrays,
at least it seems that it doesn't work right for me:

Case #1:

a = []
a << a
b = []
b << b

a == b #=> returns *false*

Is that expected or bug? The inspect values are the same.

On the other hand, when we use #dup:

Case #2:

a = [1]
a << a
b = a.dup

a == b #=> returns *true*

But if you look at the inspect values for a and b, you'll see:

a: [1, [...]]
b: [1, [1, [...]]]

This seems to be weird.

So, in the first case, the values seem to be equal, but #== returns
false for them, and
in the second case, the values seem to be different, but #== returns true. Huh?

Thanks,
  --Vladimir

In This Thread

Prev Next