From: spamscud2003@yahoo.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:86032] [Ruby trunk Bug#14588] math library functions should NOT raise exceptions
Date: Thu, 08 Mar 2018 08:03:01 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-70892.20180308080300.5c96427d1bfdbc72@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-14588.20180308052450@ruby-lang.org
Issue #14588 has been updated by Anon92929 (Anon Ymous).
Your behavior isn't acceptable.
Going on personal vendettas and threatening to get users banned from github because you didn't like how they re-opened a ticket you closed is not acceptable.
----------------------------------------
Bug #14588: math library functions should NOT raise exceptions
https://bugs.ruby-lang.org/issues/14588#change-70892
* 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/
next prev parent reply other threads:[~2018-03-08 8:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-14588.20180308052450@ruby-lang.org>
2018-03-08 5:24 ` [ruby-core:86001] [Ruby trunk Bug#14588] math library functions should NOT raise exceptions spamscud2003
2018-03-08 5:25 ` [ruby-core:86002] " spamscud2003
2018-03-08 5:33 ` [ruby-core:86003] " spamscud2003
2018-03-08 5:42 ` [ruby-core:86004] " spamscud2003
2018-03-08 5:46 ` [ruby-core:86005] " shannonskipper
2018-03-08 5:56 ` [ruby-core:86006] " spamscud2003
2018-03-08 5:58 ` [ruby-core:86007] " spamscud2003
2018-03-08 6:09 ` [ruby-core:86009] " spamscud2003
2018-03-08 6:13 ` [ruby-core:86010] " spamscud2003
2018-03-08 6:29 ` [ruby-core:86011] " duerst
2018-03-08 6:36 ` [ruby-core:86012] " spamscud2003
2018-03-08 6:39 ` [ruby-core:86013] " shannonskipper
2018-03-08 6:44 ` [ruby-core:86015] " spamscud2003
2018-03-08 6:45 ` [ruby-core:86016] " spamscud2003
2018-03-08 6:48 ` [ruby-core:86017] " spamscud2003
2018-03-08 6:50 ` [ruby-core:86018] " spamscud2003
2018-03-08 7:01 ` [ruby-core:86019] " shannonskipper
2018-03-08 7:09 ` [ruby-core:86020] " spamscud2003
2018-03-08 7:10 ` [ruby-core:86021] " spamscud2003
2018-03-08 7:13 ` [ruby-core:86022] " spamscud2003
2018-03-08 7:19 ` [ruby-core:86024] " spamscud2003
2018-03-08 7:36 ` [ruby-core:86029] " spamscud2003
2018-03-08 8:03 ` spamscud2003 [this message]
2018-03-08 10:09 ` [ruby-core:86042] " spamscud2003
2018-03-31 10:56 ` [ruby-core:86411] [Ruby trunk Bug#14588][Rejected] " nobu
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-70892.20180308080300.5c96427d1bfdbc72@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).