Issue #20444 has been updated by nobu (Nobuyoshi Nakada).
I'm curious what your use case is.
Although I don't know the reason why `StopIteration#initialize` does not have the
argument for `result`, it would be difficult to change it now because of the backward
compatibility.
----------------------------------------
Bug #20444: Kernel#loop: returning the "result" value of StopIteration
doesn't work when raised directly
https://bugs.ruby-lang.org/issues/20444#change-108075
* Author: esad (Esad Hajdarevic)
* Status: Closed
* ruby -v: ruby 3.3.0 (2023-12-25 revision 5124f9ac75) [arm64-darwin20]
* Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN
----------------------------------------
There was a
https://bugs.ruby-lang.org/issues/11498 a while ago which was merged in, but I
was surprised to find out that raising `StopIteration` in a loop like
`loop { raise StopIteration.new(3) }`
returns nil and not 3.
--
https://bugs.ruby-lang.org/