Issue #20970 has been updated by tompng (tomoya ishida). The behavior of nested `it` discussed in #20930 has changed with #20969 ~~~ [1].each { p it; [5].each { p it } } # 1, 5 # --parser=prism, (confirmed by matz at dev meeting?) # 1, 1 # --parser=parse.y (result was 1, 5 before) ~~~ So I think there is a room for discussion to fix prism or to revert the change made to parse.y. ---------------------------------------- Bug #20970: `it /1/i` raises undefined method 'it' for main (NoMethodError) even if binding.local_variables includes `it` https://bugs.ruby-lang.org/issues/20970#change-111114 * Author: tompng (tomoya ishida) * Status: Open * Assignee: prism * ruby -v: ruby 3.4.0dev (2024-12-19T07:16:12Z master 335bba0fde) +PRISM [x86_64-linux] * Backport: 3.1: DONTNEED, 3.2: DONTNEED, 3.3: DONTNEED ---------------------------------------- `it` parameter became a local variable with #20965, but it does not behave like local variable with `--parser=prism` ~~~ruby i=2 42.tap do p it # 42 p local_variables # [:it, :i] p it /1/i # should be 21, got NoMethodError end ~~~ It prints `42`, `[:it, :i], `21` with `--parser=parse.y` -- https://bugs.ruby-lang.org/