Skip to content

[Bug #21513] Raise on converting endless range to set #13902

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

viralpraxis
Copy link
Contributor

@viralpraxis viralpraxis commented Jul 15, 2025

Before this patch, trying to convert endless range (e.g. (1..) or any other inifinte enumerable) to set (using to_set) would hang

Copy link
Contributor

@jeremyevans jeremyevans left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for working on this.

range.c Outdated
range_to_set(VALUE range)
{
if (NIL_P(RANGE_END(range))) {
rb_raise(rb_eRangeError, "cannot convert endless range to a set");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe that endless range error should be the same error type as beginless range error. Calling to_set on a beginless range currently raises TypeError. This method should probably have beginless range raise RangeError instead, and include a test and an example for that.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense. Should we also tweak Range#to_a to raise RangeError in both cases?

./ruby -e '(..1).to_a'
-e:1:in 'Range#each': can't iterate from NilClass (TypeError)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense. Should we also tweak Range#to_a to raise RangeError in both cases?

@nobu what do you think?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It feels clearer for me.
@knu Any thoughts?

If we will change it too, maybe ruby/spec also needs to be updated?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should perhaps check the size of a given Enumerable in Set.new and raise an error when it is infinity.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should perhaps check the size of a given Enumerable in Set.new and raise an error when it is infinity.

Seems good to me. I'll try to follow this path

Copy link
Contributor Author

@viralpraxis viralpraxis Jul 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried out this idea and it seems to work fine (we now raise ArgumentError error for any endless enumerable, e.g. 1.upto(Float::INFINITY).

$ ./ruby -e 'Set.new((1..nil))'
-e:1:in 'Set#initialize': cannot initialize Set from a enumerable with infinite size (ArgumentError)
	from -e:1:in '<main>'
$ ./ruby -e '(1..nil).to_set'  
-e:1:in 'Enumerable#to_set': cannot initialize Set from a enumerable with infinite size (ArgumentError)
	from -e:1:in '<main>'

@viralpraxis viralpraxis force-pushed the raise-on-endless-range-to-set branch 2 times, most recently from 4b9f122 to 31a3861 Compare July 15, 2025 22:33
@viralpraxis
Copy link
Contributor Author

There's a SEGV in the ZJIT test suite: https://github.com/ruby/ruby/actions/runs/16305765996/job/46051383888?pr=13902

Not sure if it's related to my changes

@viralpraxis viralpraxis force-pushed the raise-on-endless-range-to-set branch from 31a3861 to a5a7db6 Compare July 15, 2025 22:52
@tekknolagi
Copy link
Contributor

There's a SEGV in the ZJIT test suite: https://github.com/ruby/ruby/actions/runs/16305765996/job/46051383888?pr=13902

Not sure if it's related to my changes

ZJIT error seems entirely unrelated to your change from a quick glance

@tekknolagi
Copy link
Contributor

Looks like a weird GC issue related to marking though so paging in @k0kubun for good measure

@viralpraxis viralpraxis force-pushed the raise-on-endless-range-to-set branch from a5a7db6 to e1b6f53 Compare July 15, 2025 23:39
@viralpraxis viralpraxis changed the title [Feature #21513] Raise on converting endless range to set [Bug #21513] Raise on converting endless range to set Jul 15, 2025
@viralpraxis viralpraxis force-pushed the raise-on-endless-range-to-set branch from e1b6f53 to ca35402 Compare July 15, 2025 23:40

This comment has been minimized.

@k0kubun
Copy link
Member

k0kubun commented Jul 16, 2025

I agree that it's probably not related to the changes. We're looking into GC issues with ZJIT.

@viralpraxis viralpraxis force-pushed the raise-on-endless-range-to-set branch 4 times, most recently from 4fcebf3 to 76fe90b Compare July 17, 2025 15:12
ref: https://bugs.ruby-lang.org/issues/21513

Before this patch, trying to convert endless range (e.g. `(1..)`) to set
(using `to_set`) would hang
@viralpraxis viralpraxis force-pushed the raise-on-endless-range-to-set branch from 76fe90b to 7753557 Compare July 17, 2025 15:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants