Bug #20748
closed
Issue with defined? given method call with block in prism compiler
Added by luke-gru (Luke Gruber) about 2 months ago.
Updated about 2 months ago.
Description
test.rb
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
- 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:
puts defined?(undefined_method(){}) # => "expression"
puts defined?(undefined_method(&b)) # => ""
whereas Prism results in:
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.
I agree it's weird but it could cause an incompatibility I guess, defined?()
is a weird one for sure.
- Status changed from Open to Closed
Also available in: Atom
PDF
Like0
Like0Like0Like0