From: hsbt@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:83723] [Ruby trunk Feature#13984][Assigned] BigDecimal should be immutable/frozen and return itself on #dup
Date: Fri, 10 Nov 2017 07:12:16 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-67759.20171110071215.13d67a68db53e1f1@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-13984.20171006205846@ruby-lang.org
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/
next prev parent reply other threads:[~2017-11-10 7:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2017-12-13 2:45 ` [ruby-core:84230] " muraken
2017-12-13 4:12 ` [ruby-core:84231] " muraken
2018-12-07 2:23 ` [ruby-core:90351] [Ruby trunk Feature#13984][Closed] " muraken
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-67759.20171110071215.13d67a68db53e1f1@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).