[#42344] [ruby-trunk - Feature #5964][Open] Make Symbols an Alternate Syntax for Strings — Tom Wardrop <tom@...>

23 messages 2012/02/03

[#42443] [ruby-trunk - Bug #5985][Open] miniruby skews "make benchmark" results — Eric Wong <normalperson@...>

21 messages 2012/02/08

[#42444] [ruby-trunk - Bug #5986][Open] Segmentation Fault — Luis Matta <levmatta@...>

16 messages 2012/02/08

[#42471] [ruby-trunk - Feature #5995][Open] calling io_advise_internal() in read_all() — Masaki Matsushita <glass.saga@...>

20 messages 2012/02/10

[#42560] [ruby-trunk - Bug #6011][Open] ruby-1.9.3-p0/lib/webrick/utils.rb:184: [BUG] Segmentation fault — Vit Ondruch <v.ondruch@...>

12 messages 2012/02/13

[#42579] [ruby-trunk - Bug #6012][Open] Proc#source_location also return the column — Roger Pack <rogerpack2005@...>

14 messages 2012/02/14

[#42685] [ruby-trunk - Bug #6036][Open] Test failures in Fedora Rawhide/17 — Bohuslav Kabrda <bkabrda@...>

14 messages 2012/02/16

[#42697] [ruby-trunk - Bug #6040][Open] Transcoding test failure: Big5 to UTF8 not defined (MinGW) — Luis Lavena <luislavena@...>

10 messages 2012/02/16

[#42813] [ruby-trunk - Feature #6065][Open] Allow Bignum marshalling/unmarshalling from C API — Martin Bosslet <Martin.Bosslet@...>

22 messages 2012/02/23

[#42815] [ruby-trunk - Bug #6066][Open] Fix "control may reach end of non-void function" warnings for clang — Eric Hodel <[email protected]>

15 messages 2012/02/23

[#42857] [ruby-trunk - Feature #6074][Open] Allow alias arguments to have a comma — Thomas Sawyer <transfire@...>

20 messages 2012/02/24

[#42891] [ruby-trunk - Feature #6083][Open] Hide a Bignum definition — Koichi Sasada <redmine@...>

23 messages 2012/02/25

[#42906] [ruby-trunk - Bug #6085][Open] Treatment of Wrong Number of Arguments — Marc-Andre Lafortune <ruby-core@...>

14 messages 2012/02/25

[#42949] [ruby-trunk - Bug #6089][Open] Test suite fails with OpenSSL 1.0.1 — Vit Ondruch <v.ondruch@...>

13 messages 2012/02/26

[ruby-core:42621] [ruby-trunk - Feature #1844][Rejected] Immediates Should Not Respond to :dup

From: Yusuke Endoh <mame@...>
Date: 2012-02-14 13:16:04 UTC
List: ruby-core #42621
Issue #1844 has been updated by Yusuke Endoh.

Status changed from Assigned to Rejected

I'm rejecting this feature ticket because no progress has been
made for a long time.  See [ruby-core:42391].



My personal opinion.

I might miss somthing, but I cannot understand the motivation
well.  When we duplicate an object, we then usually modify the
object, don't we?  To modify them, we must eventually check the
type.  I wonder why this feature is needed.

It makes no sense (to me) to compare a method that raises
NotImplementedError with Immediate.dup.  They are different.
In an extreme case, Kernel#raise always raise an exception.
Do you think respond_to?(:raise) should return false?

-- 
Yusuke Endoh <[email protected]>
----------------------------------------
Feature #1844: Immediates Should Not Respond to :dup
https://bugs.ruby-lang.org/issues/1844

Author: Run Paint Run Run
Status: Rejected
Priority: Low
Assignee: Yukihiro Matsumoto
Category: 
Target version: 2.0.0
ruby -v: ruby 1.9.2dev (2009-07-08 trunk 23995) [i686-linux]


=begin
 Immediate can't be dup'd but they :respond_to?(:dup). This leads to ugly logic for determining whether a value can be dup'd. I suggest that immediates return false for :respond_to?(:dup). This is consistent with methods that would raise a NotImplementedError returning false for #respond_to?.
=end



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

In This Thread

Prev Next