[#83773] [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769 — usa@...
Issue #14108 has been updated by usa (Usaku NAKAMURA).
9 messages
2017/11/15
[#83774] Re: [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769
— Eric Wong <normalperson@...>
2017/11/15
usa@garbagecollect.jp wrote:
[#83775] Re: [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769
— "U.NAKAMURA" <usa@...>
2017/11/15
Hi, Eric
[#83779] Re: [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769
— Eric Wong <normalperson@...>
2017/11/15
"U.NAKAMURA" <usa@garbagecollect.jp> wrote:
[#83781] Re: [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769
— "U.NAKAMURA" <usa@...>
2017/11/15
Hi, Eric,
[#83782] Re: [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769
— Eric Wong <normalperson@...>
2017/11/15
"U.NAKAMURA" <usa@garbagecollect.jp> wrote:
[ruby-core:83723] [Ruby trunk Feature#13984][Assigned] BigDecimal should be immutable/frozen and return itself on #dup
From:
hsbt@...
Date:
2017-11-10 07:12:16 UTC
List:
ruby-core #83723
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/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>