Bug #16854: Using (...) when the method name is a keyword generates error - Ruby master - Ruby Issue Tracking System

Actions

Copy link

Bug #16854

closed

Using (...) when the method name is a keyword generates error

Added by jamesnakagawa (James Nakagawa) almost 4 years ago. Updated over 3 years ago.

Status:

Closed

Assignee:

Target version:

ruby -v:

2.7.0

Backport:

2.5: DONTNEED, 2.6: DONTNEED, 2.7: DONE

[ruby-core:98323]

Description

Although I wouldn't generally recommend it, naming a method true is allowed. However, in combination with the new argument forwarding keyword ..., a syntax error is generated which does not occur with other argument choices.

This came up for me on my Rails project where an enumerated database column was defined to allow the values :true, :false (not an unreasonable request in itself). Active Record's generated class tried to contain methods by these names.

Try this code for yourself:

class Works
  def true(*args)
    puts(*args)
  end
end

Works.new.true 1, 2, 3
# => 1, 2, 3

class WontWork
  def true(...)
    puts(...)
  end
end

# => freezes