From: shannonskipper@... Date: 2018-03-08T07:01:46+00:00 Subject: [ruby-core:86019] [Ruby trunk Bug#14588] math library functions should NOT raise exceptions Issue #14588 has been updated by shan (Shannon Skipper). Your behavior isn't acceptable. Do not open new issues when your issue is closed and locked. It is very bad manners. > I'm so sorry, that I reported, as a bug, the fact that my code started breaking because I updated BigDecimal and it choked on a random NaN. ~~~ ruby BigDecimal::VERSION #=> "1.3.4" BigDecimal(Float::NAN) #=> NaN ~~~ If you'd like to learn Ruby, and understand why it is how it is, we'd be happy to help in the #ruby channel on freenode.net. Or you could ask on the mailing list. What you're doing here isn't a good way to learn. Harassing maintainers will get you banned from Github entirely. This issue should be closed as a duplicate of #14587. ---------------------------------------- Bug #14588: math library functions should NOT raise exceptions https://bugs.ruby-lang.org/issues/14588#change-70880 * Author: Anon92929 (Anon Ymous) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN ---------------------------------------- BigDecimal, Integer, Float, none of these should raise exceptions, but they should all fail SILENTLY or return NaN during error cases. I shouldn't have to go fix every possible way that BigDecimal might throw a breaking change in a thousand places in my codebase. I need math libraries that DON'T BREAK!!! BUG RESUBMITTED. The bug was rejected at github because I was referred to open a ticket at ruby-lang.org. The bug was rejectet at ruby-lang.org because the ticket was closed at github. Not cool, guys. -- https://bugs.ruby-lang.org/ Unsubscribe: