ruby.git/enumerator.c, branch v4.0.3 The Ruby Programming Language [Backport #21866] Fix integer overflow checks in enumerator (#16088) 2026-02-09T17:47:03+00:00 Randy Stauner randy@r4s6.net 2026-02-09T17:47:03+00:00 584c3b6465ec40226687e9699d2b652d9ad31a8f Fix integer overflow checks in enumerator Co-authored-by: Jörmungandrk <github@zerodaysec.org> 
Fix integer overflow checks in enumerator

Co-authored-by: Jörmungandrk <github@zerodaysec.org>
 Add clarifications about the Enumerator.size (#15615) 2025-12-20T11:26:12+00:00 Victor Shepelev zverok.offline@gmail.com 2025-12-20T11:26:12+00:00 a57039196f0ef5a3ee8710d85e52e8644b9bc0c2 






Revert the default size of Enumerator::Producer to infinity
2025-12-17T09:56:22+00:00

Akinori Musha
knu@idaemons.org

2025-12-17T09:36:10+00:00

c99670d6683fec770271d35c2ae082514b1abce3

[Bug #21780]





[Bug #21780]







Revert the override of Enumerator#to_set that performed size checks
2025-12-17T08:30:24+00:00

Akinori Musha
knu@idaemons.org

2025-12-17T08:30:24+00:00

79f36c544a0431d9b76c3c11a5f622383eaca7bd

[Bug #21780]





[Bug #21780]







Enumerator.produce accepts an optional `size` keyword argument
2025-12-13T14:33:09+00:00

Akinori Musha
knu@idaemons.org

2025-11-20T14:36:21+00:00

79a6ec74831cc47d022b86dfabe3c774eaaf91ca

When not specified, the size is unknown (`nil`).  Previously, the size was always `Float::INFINITY` and not specifiable.

[Feature #21701]





When not specified, the size is unknown (`nil`).  Previously, the size was always `Float::INFINITY` and not specifiable.

[Feature #21701]







Add size checks to Range#to_set and Enumerator#to_set [Bug #21654]
2025-11-13T13:00:07+00:00

Akinori Musha
knu@idaemons.org

2025-11-13T11:01:37+00:00

61500c6f48135ef018f5e496ff292a86b0043c65

These two class are most common sources of infinite sequences.  This change should effectively prevent accidental infinite loops when calling to_set on them. [Bug #21513]





These two class are most common sources of infinite sequences.  This change should effectively prevent accidental infinite loops when calling to_set on them. [Bug #21513]







Make Enumerator::Product write-barrier protected
2025-08-12T17:32:41+00:00

Peter Zhu
peter@peterzhu.ca

2025-08-12T14:16:55+00:00

a9230e76ee19716c7d2e035be7bd1be9bdca2b59












Make Enumerator::Chain write-barrier protected
2025-08-12T17:32:41+00:00

Peter Zhu
peter@peterzhu.ca

2025-08-12T14:14:57+00:00

3e1e2bda49724c619cbb82935b2a11254e810b6c












Convert `Enumerator` types to use `rb_gc_mark_and_move`
2025-08-07T19:00:00+00:00

Jean Boussier
jean.boussier@gmail.com

2025-08-07T12:41:21+00:00

aee8e65c702283af8a70cb1fdac0797aa7c75001

The `p->field = rb_gc_location(p->field)` isn't ideal because it means all
references are rewritten on compaction, regardless of whether the referenced
object has moved. This isn't good for caches nor for Copy-on-Write.

`rb_gc_mark_and_move` avoid needless writes, and most of the time allow to
have a single function for both marking and updating references.





The `p->field = rb_gc_location(p->field)` isn't ideal because it means all
references are rewritten on compaction, regardless of whether the referenced
object has moved. This isn't good for caches nor for Copy-on-Write.

`rb_gc_mark_and_move` avoid needless writes, and most of the time allow to
have a single function for both marking and updating references.







Extract checks for the block in lazy enumerator
2025-07-28T08:54:09+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2025-07-28T08:54:09+00:00

1a68f1b199e48dce755015eff2dfa8828f38714d