From: Yui NARUSE <naruse@...>
Date: 2011-08-02T19:28:15+09:00
Subject: [ruby-core:38703] [Ruby 1.9 - Bug #5146][Assigned]  Bug in Set#== on ruby 1.9.3-preview1


Issue #5146 has been updated by Yui NARUSE.

Category set to lib
Status changed from Open to Assigned
Assignee set to Akinori MUSHA
Target version set to 1.9.3

Don't worry, ruby-core is also a correct bug reporting place.
(and we can make a ticket from mail)

Your account is locked (I don't why), so I unlocked it and resent the account information
----------------------------------------
Bug #5146:  Bug in Set#== on ruby 1.9.3-preview1
http://redmine.ruby-lang.org/issues/5146

Author: Bernard LAMBEAU
Status: Assigned
Priority: Normal
Assignee: Akinori MUSHA
Category: lib
Target version: 1.9.3
ruby -v: -


 Hi!
 
 Sorry for reporting this bug here, but I can't log into redmine even after
 having
 requested a new password...
 
 Set#== seems buggy in ruby 1.9.3, as illustrated by the following scenario.
 I can't reproduce the bug without using Hash#delete to get another empty
 hash
 than "{ }".
 
 blambeau@kali:~/Temp$ cat test.rb
 
 require 'set'
 RUBY_VERSION
 tuple = {:hello => "world"}
 empty = tuple.dup
 empty.delete(:hello)
 puts empty == {}
 puts Set.new([{}]) == Set.new([empty])
 
 blambeau@kali:~/Temp$ ruby --version
 ruby 1.9.2p290 (2011-07-09 revision 32553) [i686-linux]
 
 blambeau@kali:~/Temp$ ruby test.rb
 true
 true
 
 [...]
 
 blambeau@kali:~/Temp$ ruby --version
 ruby 1.9.3dev (2011-07-31 revision 32789) [i686-linux]
 
 blambeau@kali:~/Temp$ ruby test.rb
 true
 false


-- 
http://redmine.ruby-lang.org