* [ruby-core:83168] [Ruby trunk Feature#13984] BigDecimal should be immutable/frozen and return itself on #dup
[not found] <redmine.issue-13984.20171006205846@ruby-lang.org>
@ 2017-10-06 20:58 ` eregontp
2017-11-10 7:12 ` [ruby-core:83723] [Ruby trunk Feature#13984][Assigned] " hsbt
` (3 subsequent siblings)
4 siblings, 0 replies; 5+ messages in thread
From: eregontp @ 2017-10-06 20:58 UTC (permalink / raw)
To: ruby-core
Issue #13984 has been reported by Eregon (Benoit Daloze).
----------------------------------------
Feature #13984: BigDecimal should be immutable/frozen and return itself on #dup
https://bugs.ruby-lang.org/issues/13984
* Author: Eregon (Benoit Daloze)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
----------------------------------------
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.
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* [ruby-core:83723] [Ruby trunk Feature#13984][Assigned] BigDecimal should be immutable/frozen and return itself on #dup
[not found] <redmine.issue-13984.20171006205846@ruby-lang.org>
2017-10-06 20:58 ` [ruby-core:83168] [Ruby trunk Feature#13984] BigDecimal should be immutable/frozen and return itself on #dup eregontp
@ 2017-11-10 7:12 ` hsbt
2017-12-13 2:45 ` [ruby-core:84230] [Ruby trunk Feature#13984] " muraken
` (2 subsequent siblings)
4 siblings, 0 replies; 5+ messages in thread
From: hsbt @ 2017-11-10 7:12 UTC (permalink / raw)
To: ruby-core
Issue #13984 has been updated by hsbt (Hiroshi SHIBATA).
Status changed from Open to Assigned
Assignee set to mrkn (Kenta Murata)
----------------------------------------
Feature #13984: BigDecimal should be immutable/frozen and return itself on #dup
https://bugs.ruby-lang.org/issues/13984#change-67759
* Author: Eregon (Benoit Daloze)
* Status: Assigned
* Priority: Normal
* Assignee: mrkn (Kenta Murata)
* Target version:
----------------------------------------
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.
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* [ruby-core:84230] [Ruby trunk Feature#13984] BigDecimal should be immutable/frozen and return itself on #dup
[not found] <redmine.issue-13984.20171006205846@ruby-lang.org>
2017-10-06 20:58 ` [ruby-core:83168] [Ruby trunk Feature#13984] BigDecimal should be immutable/frozen and return itself on #dup eregontp
2017-11-10 7:12 ` [ruby-core:83723] [Ruby trunk Feature#13984][Assigned] " hsbt
@ 2017-12-13 2:45 ` muraken
2017-12-13 4:12 ` [ruby-core:84231] " muraken
2018-12-07 2:23 ` [ruby-core:90351] [Ruby trunk Feature#13984][Closed] " muraken
4 siblings, 0 replies; 5+ messages in thread
From: muraken @ 2017-12-13 2:45 UTC (permalink / raw)
To: ruby-core
Issue #13984 has been updated by mrkn (Kenta Murata).
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.
----------------------------------------
Feature #13984: BigDecimal should be immutable/frozen and return itself on #dup
https://bugs.ruby-lang.org/issues/13984#change-68356
* Author: Eregon (Benoit Daloze)
* Status: Assigned
* Priority: Normal
* Assignee: mrkn (Kenta Murata)
* Target version:
----------------------------------------
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.
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* [ruby-core:84231] [Ruby trunk Feature#13984] BigDecimal should be immutable/frozen and return itself on #dup
[not found] <redmine.issue-13984.20171006205846@ruby-lang.org>
` (2 preceding siblings ...)
2017-12-13 2:45 ` [ruby-core:84230] [Ruby trunk Feature#13984] " muraken
@ 2017-12-13 4:12 ` muraken
2018-12-07 2:23 ` [ruby-core:90351] [Ruby trunk Feature#13984][Closed] " muraken
4 siblings, 0 replies; 5+ messages in thread
From: muraken @ 2017-12-13 4:12 UTC (permalink / raw)
To: ruby-core
Issue #13984 has been updated by mrkn (Kenta Murata).
The corresponding issue in GitHub: https://github.com/ruby/bigdecimal/issues/84
----------------------------------------
Feature #13984: BigDecimal should be immutable/frozen and return itself on #dup
https://bugs.ruby-lang.org/issues/13984#change-68357
* Author: Eregon (Benoit Daloze)
* Status: Assigned
* Priority: Normal
* Assignee: mrkn (Kenta Murata)
* Target version:
----------------------------------------
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.
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* [ruby-core:90351] [Ruby trunk Feature#13984][Closed] BigDecimal should be immutable/frozen and return itself on #dup
[not found] <redmine.issue-13984.20171006205846@ruby-lang.org>
` (3 preceding siblings ...)
2017-12-13 4:12 ` [ruby-core:84231] " muraken
@ 2018-12-07 2:23 ` muraken
4 siblings, 0 replies; 5+ messages in thread
From: muraken @ 2018-12-07 2:23 UTC (permalink / raw)
To: ruby-core
Issue #13984 has been updated by mrkn (Kenta Murata).
Status changed from Assigned to Closed
Fixed in r66222
----------------------------------------
Feature #13984: BigDecimal should be immutable/frozen and return itself on #dup
https://bugs.ruby-lang.org/issues/13984#change-75462
* Author: Eregon (Benoit Daloze)
* Status: Closed
* Priority: Normal
* Assignee: mrkn (Kenta Murata)
* Target version:
----------------------------------------
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.
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2018-12-07 2:24 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <redmine.issue-13984.20171006205846@ruby-lang.org>
2017-10-06 20:58 ` [ruby-core:83168] [Ruby trunk Feature#13984] BigDecimal should be immutable/frozen and return itself on #dup eregontp
2017-11-10 7:12 ` [ruby-core:83723] [Ruby trunk Feature#13984][Assigned] " hsbt
2017-12-13 2:45 ` [ruby-core:84230] [Ruby trunk Feature#13984] " muraken
2017-12-13 4:12 ` [ruby-core:84231] " muraken
2018-12-07 2:23 ` [ruby-core:90351] [Ruby trunk Feature#13984][Closed] " muraken
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).