[ruby-core:78312] [Ruby trunk Bug#11929][Closed] No programatic way to check ability to dup/clone an object

From: matz@...
Date: 2016-11-25 07:24:03 UTC
List: ruby-core #78312
Issue #11929 has been updated by Yukihiro Matsumoto.

Status changed from Feedback to Closed

The issue closed by #12979

Matz.


----------------------------------------
Bug #11929: No programatic way to check ability to dup/clone an object
https://bugs.ruby-lang.org/issues/11929#change-61676

* Author: xavier nayrac
* Status: Closed
* Priority: Normal
* Assignee: Yukihiro Matsumoto
* ruby -v: ruby 2.3.0dev (2015-12-06 trunk 52904) [i686-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
We can't dup a Fixnum, and it's ok. But I'm wondering 束why is Fixnum saying it can dup?損

~~~
1.respond_to?(:dup) #=> true
~~~

Don't you think that the `dup` method should be undefined in the class Fixnum?

Currently I can do `class Fixnum; undef :dup; end`, but that should be in the core Ruby, isn't it?




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

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread

Prev Next