[#85940] [Ruby trunk Bug#14578] Forking a child process inside of a mutex crashes the ruby interpreter — ben.govero@...
Issue #14578 has been reported by bengovero (Ben Govero).
3 messages
2018/03/05
[#86205] [Ruby trunk Feature#14618] Add display width method to String for CLI — aycabta@...
SXNzdWUgIzE0NjE4IGhhcyBiZWVuIHJlcG9ydGVkIGJ5IGF5Y2FidGEgKGF5Y2FidGEgLikuCgot
3 messages
2018/03/19
[#86366] Re: [ruby-cvs:70102] usa:r63008 (trunk): get rid of test error/failure on Windows introduced at r62955 — Eric Wong <normalperson@...>
[email protected] wrote:
3 messages
2018/03/28
[ruby-core:86013] [Ruby trunk Bug#14588] math library functions should NOT raise exceptions
From:
shannonskipper@...
Date:
2018-03-08 06:39:16 UTC
List:
ruby-core #86013
Issue #14588 has been updated by shan (Shannon Skipper). Kernel methods like `Float()`, `Integer()`, and `BigDecimal()` are all explicitly for the purpose of ensure strict conformance with numeric representation. Each of these Kernel methods raise a `TypeError` when the argument does not strictly conform. That's how they work. That's how they're meant to work. If you're using them when you don't want strict conformance, you're doing it wrong. As pointed out in the Github issue, the proper method to use for your purpose is `#to_d`. ---------------------------------------- Bug #14588: math library functions should NOT raise exceptions https://bugs.ruby-lang.org/issues/14588#change-70875 * 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: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>