Skip to content

Commit

Permalink
explains the motivation for duplicable?
Browse files Browse the repository at this point in the history
  • Loading branch information
fxn committed Nov 18, 2009
1 parent 5446d5c commit 2ddbef4
Showing 1 changed file with 16 additions and 0 deletions.
16 changes: 16 additions & 0 deletions activesupport/lib/active_support/core_ext/object/duplicable.rb
Original file line number Diff line number Diff line change
@@ -1,3 +1,19 @@
# Most objects are cloneable, but not all. For example you can't dup +nil+:
#
# nil.dup # => TypeError: can't dup NilClass
#
# Classes may signal their instances are not duplicable removing +dup+/+clone+
# or raising exceptions from them. So, to dup an arbitrary object you normally
# use an optimistic approach and are ready to catch an exception, say:
#
# arbitrary_object.dup rescue object
#
# Rails dups objects in a few critical spots where they are not that arbitrary.
# That rescue is very expensive (like 40 times slower than a predicate), and it
# is often triggered.
#
# That's why we hardcode the following cases and check duplicable? instead of
# using that rescue idiom.
class Object
# Can you safely .dup this object?
# False for nil, false, true, symbols, numbers, class and module objects; true otherwise.
Expand Down

0 comments on commit 2ddbef4

Please sign in to comment.