From: "trans (Thomas Sawyer)" <transfire@...>
Date: 2013-01-03T12:10:19+09:00
Subject: [ruby-core:51227] [ruby-trunk - Bug #5759] flatten calls to_ary on everything


Issue #5759 has been updated by trans (Thomas Sawyer).


=begin
So it does call (({#respond_to?})) after all? Yet, I thought (({#respond_to_missing?})) was invented so people would not have to override (({#respond_to?})). What's my misunderstanding? Surely we are not now expected to define both?
=end

----------------------------------------
Bug #5759: flatten calls to_ary on everything
https://bugs.ruby-lang.org/issues/5759#change-35185

Author: trans (Thomas Sawyer)
Status: Rejected
Priority: Normal
Assignee: nobu (Nobuyoshi Nakada)
Category: 
Target version: 1.9.3
ruby -v: ruby 1.9.3dev (2011-09-23 revision 33323) [x86_64-linux]


I often ensure that I have an array by doing:

  def foo=(x)
    @foo = [x].flatten
  end

But this has turned into a problem as of late, as it seems #flatten is calling #to_ary on every element in the array, and apparently catching the error raised if #to_ary isn't defined for that object. But that causes potential issues with objects that use #method_missing. I think #flatten should use `respond_to?(:to_ary)` to make sure an object can handle it before actually calling it.



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