From: "mame (Yusuke Endoh)" <mame@...>
Date: 2012-03-27T02:34:23+09:00
Subject: [ruby-core:43705] [ruby-trunk - Feature #5185][Assigned] Set#merge acts in place but Hash#merge does not


Issue #5185 has been updated by mame (Yusuke Endoh).

Status changed from Open to Assigned
Assignee set to knu (Akinori MUSHA)

I understand the problem, but I guess it is too late to fix it.
Anyway, I'm assigning this to knu, the maintainer of lib/set.rb.

-- 
Yusuke Endoh <mame@tsg.ne.jp>
----------------------------------------
Feature #5185: Set#merge acts in place but Hash#merge does not
https://bugs.ruby-lang.org/issues/5185#change-25206

Author: trans (Thomas Sawyer)
Status: Assigned
Priority: Normal
Assignee: knu (Akinori MUSHA)
Category: lib
Target version: 2.0.0


Waste of brain cells to have to learn and recall they are different. The expected method would be Set#merge!, Set#merge would return a new Set instance.

OTOH, why not Set#concat ? Or conversely, Array#merge ?




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