Project

General

Profile

Actions
Copy link

Feature #13984

closed

BigDecimal should be immutable/frozen and return itself on #dup

Feature #13984: BigDecimal should be immutable/frozen and return itself on #dup

Added by Eregon (Benoit Daloze) about 8 years ago. Updated almost 7 years ago.

Status:
Closed
Assignee:
mrkn (Kenta Murata)
Target version:
-
[ruby-core:83168]

Description

Currently, BigDecimal instances are not frozen, and supports #dup by returning a new instance.

In the spirit of #12979 and #13983, I think BigDecimal instances should always be frozen.
Then BigDecimal#dup/clone should just return the same instance.

Related issues 1 (0 open — 1 closed)

Related to Ruby - Feature #13985: Avoid exception for #dup/#clone on Rational and ComplexClosedActions

Updated by Eregon (Benoit Daloze) about 8 years ago Actions
Copy link
 #1

  • Related to Feature #13985: Avoid exception for #dup/#clone on Rational and Complex added

Updated by hsbt (Hiroshi SHIBATA) almost 8 years ago Actions
Copy link
 #2 [ruby-core:83723]

  • Status changed from Open to Assigned
  • Assignee set to mrkn (Kenta Murata)

Updated by mrkn (Kenta Murata) almost 8 years ago Actions
Copy link
 #3 [ruby-core:84230]

I decided to make a BigDecimal is frozen and remove dup-support.
But it introduces incompatibilities, so during Ruby 2.5 period, I'll make them deprecated and issue warning messages.

Updated by mrkn (Kenta Murata) almost 8 years ago Actions
Copy link
 #5

  • Target version set to 2.6

Updated by naruse (Yui NARUSE) almost 8 years ago Actions
Copy link
 #6

  • Target version deleted (2.6)

Updated by mrkn (Kenta Murata) almost 7 years ago Actions
Copy link
 #7 [ruby-core:90351]

  • Status changed from Assigned to Closed

Fixed in r66222

Actions
Copy link

Also available in: PDF Atom