ruby-dev

Download

ruby-dev@ml.ruby-lang.org

February 2025

1 participants
2 discussions

[ruby-dev:52150] [Ruby master Bug#21138] The modifier expression with "it" is parsed differently in parse.y and Prism, which is unexpected in both.
by kinoppyd (Yasuhiro Kinoshita) 14 Feb '25

14 Feb '25

Issue #21138 has been reported by kinoppyd (Yasuhiro Kinoshita). ---------------------------------------- Bug #21138: The modifier expression with "it" is parsed differently in parse.y and Prism, which is unexpected in both. https://bugs.ruby-lang.org/issues/21138 * Author: kinoppyd (Yasuhiro Kinoshita) * Status: Open * ruby -v: ruby 3.4.1 (2024-12-25 revision 48d4efcb85) [arm64-darwin21] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- ## Actual ### parse.y In parse.y, the block parameter "it" behaves as if it is not assigned. ```ruby # parse.y loop.rb:1:in 'block in <main>': undefined method '<' for nil (NoMethodError) 1.then { it *= 10 while it < 1000 } ^ from <internal:kernel>:126:in 'Kernel#then' from loop.rb:1:in '<main>' ``` ### prism In Prism, I may not understand what's happening due to my limited knowledge, but it results in a syntax error." ```ruby unexpected integer; expected an expression after the operator unexpected integer, expecting end-of-input > 1 1.then { it *= 10 while it < 1000 } loop.rb:1: syntax errors found (SyntaxError) > 1 | 1.then { it *= 10 while it < 1000 } | ^~ unexpected integer; expected an expression after the operator | ^~ unexpected integer, expecting end-of-input ``` ## Expected 'It' should be reassigned until it is greater than 1000. -- https://bugs.ruby-lang.org/

2 2

[ruby-dev:52146] [Ruby master Bug#21123] instance_exec with curried proc
by taichi730 (Taichi Ishitani) 09 Feb '25

09 Feb '25

Issue #21123 has been reported by taichi730 (Taichi Ishitani). ---------------------------------------- Bug #21123: instance_exec with curried proc https://bugs.ruby-lang.org/issues/21123 * Author: taichi730 (Taichi Ishitani) * Status: Open * ruby -v: 3.4.1 (2024-12-25 revision 48d4efcb85) +PRISM [x86_64-linux] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- I have a question about behavior of `#instance_exec` with a curried proc. When running `#instance_exex` with a curried proc, it appears that the given proc is executed on the context where it is created but not the receiver object. Example code: ```ruby a = Object.new def a.foo(n) p end b = proc { |n| foo(n) }.curry a.instance_exec(0, &b) ``` Execution result: ``` $ ruby test.rb test.rb:6:in 'block in <main>': undefined method 'foo' for main (NoMethodError) b = proc { |n| foo(n) }.curry ^^^ Did you mean? for from test.rb:7:in 'BasicObject#instance_exec' from test.rb:7:in '<main>' ``` Is this intentional behavior? I expect that the given curried proc is also executed on the context of the receiver object like a non-curried proc. -- https://bugs.ruby-lang.org/

3 3