Issue #20748 has been updated by kddnewton (Kevin Newton). Assignee set to kddnewton (Kevin Newton) I have opened a PR for this to match the behavior exactly, but I will say I think Prism's behavior is actually correct here. Right now compile.c results in: ```ruby puts defined?(undefined_method(){}) # => "expression" puts defined?(undefined_method(&b)) # => "" ``` whereas Prism results in: ```ruby puts defined?(undefined_method(){}) # => "" puts defined?(undefined_method(&b)) # => "" ``` I have updated the code to match compile.c, but I think it's incorrect that we are falling back to "expression" because it has an explicit block versus an implicit one. ---------------------------------------- Bug #20748: Issue with defined? given method call with block in prism compiler https://bugs.ruby-lang.org/issues/20748#change-109801 * Author: luke-gru (Luke Gruber) * Status: Open * Assignee: kddnewton (Kevin Newton) * ruby -v: 3.4.0dev * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- test.rb ```ruby puts defined?(undefined_method(){}) ``` ``` ./ruby --parser=parse.y -I../ruby/lib -I. -I.ext/x86_64-linux -I.ext/common -r./x86_64-linux-fake ../ruby/test.rb expression ``` ``` ./ruby --parser=prism -I../ruby/lib -I. -I.ext/x86_64-linux -I.ext/common -r./x86_64-linux-fake ../ruby/test.rb # empty line ``` -- https://bugs.ruby-lang.org/