Actions
Bug #16854
closed
Using (...) when the method name is a keyword generates error
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
Updated by 
Updated by 
Updated by
Actions
Like0
Like0Like0Like0Like0Like0