From: janosch84@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:93156] [Ruby trunk Bug#15807] Range#minmax is slow and never returns for endless ranges
Date: Sat, 15 Jun 2019 09:50:25 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-78599.20190615095024.30333d7e461fa04a@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15807.20190428121410@ruby-lang.org
Issue #15807 has been updated by janosch-x (Janosch Müller).
jeremyevans0 (Jeremy Evans) wrote:
> I think this is a bug we should fix, even if it breaks code relying on this bug ("all bug fixes are incompatibilities" :)).
Yes, it is a bit reminiscent of https://xkcd.com/1172/ :)
> Does anyone have an opinion on whether `minmax` should call overridden `min` and `max` methods? Or do we expect if you override `min` or `max`, you should also override `minmax`? I don't have a strong opinion either way.
Other classes including Enumerable also require `minmax` to be overridden individually. `Set` or `SortedSet` are examples from the stdlib. So I guess it would be more consistent to call the C functions.
----------------------------------------
Bug #15807: Range#minmax is slow and never returns for endless ranges
https://bugs.ruby-lang.org/issues/15807#change-78599
* Author: janosch-x (Janosch Müller)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: 2.6.3p62
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
current situation:
- `(1..).minmax` runs forever
- `(1..).max` raises "cannot get the maximum of endless range"
- `(1..Float::INFINITY).minmax` runs forever
- `(1..Float::INFINITY).max` returns instantly
- `(1..1_000_000_000).minmax` takes one minute
- `(1..1_000_000_000).max` returns instantly
my suggestion:
- implement `minmax` in range.c, return [`range_min`, `range_max`]
- for endless ranges, this will trigger the same error as `max` does
- delegate to enum (rb_call_super) only if called with a block (?)
i could perhaps provide a PR if you can point me to some information on how to contribute.
cheers!
---Files--------------------------------
range-minmax.patch (2.89 KB)
--
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>
next prev parent reply other threads:[~2019-06-15 9:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15807.20190428121410@ruby-lang.org>
2019-04-28 12:14 ` [ruby-core:92459] [Ruby trunk Bug#15807] Range#minmax is slow and never returns for endless ranges janosch84
2019-04-28 12:32 ` [ruby-core:92461] " mame
2019-04-28 14:29 ` [ruby-core:92463] " janosch84
2019-05-31 19:31 ` [ruby-core:92916] " mohsen
2019-06-08 5:24 ` [ruby-core:93021] " merch-redmine
2019-06-15 9:50 ` janosch84 [this message]
2019-06-16 13:26 ` [ruby-core:93181] " janosch84
2019-06-18 14:08 ` [ruby-core:93224] " eregontp
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-78599.20190615095024.30333d7e461fa04a@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).