[ruby-core:98323] [Ruby master Bug#16854] Using (...) when the method name is a keyword generates error

[ruby-core:98323] [Ruby master Bug#16854] Using (...) when the method name is a keyword generates error

[james]

Issue #16854 has been reported by jamesnakagawa (James Nakagawa).

----------------------------------------
Bug #16854: Using (...) when the method name is a keyword generates error
https://bugs.ruby-lang.org/issues/16854

* Author: jamesnakagawa (James Nakagawa)
* Status: Open
* Priority: Normal
* ruby -v: 2.7.0
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
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:

```ruby
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
```



-- 
https://bugs.ruby-lang.org/

[ruby-core:98325] [Ruby master Bug#16854] Using (...) when the method name is a keyword generates error

[shevegen]

Issue #16854 has been updated by shevegen (Robert A. Heiler).


Interesting find and explanation.

----------------------------------------
Bug #16854: Using (...) when the method name is a keyword generates error
https://bugs.ruby-lang.org/issues/16854#change-85563

* Author: jamesnakagawa (James Nakagawa)
* Status: Open
* Priority: Normal
* ruby -v: 2.7.0
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
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:

```ruby
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
```



-- 
https://bugs.ruby-lang.org/

[ruby-core:98379] [Ruby master Bug#16854] Using (...) when the method name is a keyword generates error

[nobu]

Issue #16854 has been updated by nobu (Nobuyoshi Nakada).


It results in a syntax error, right?

https://github.com/ruby/ruby/pull/3112

----------------------------------------
Bug #16854: Using (...) when the method name is a keyword generates error
https://bugs.ruby-lang.org/issues/16854#change-85647

* Author: jamesnakagawa (James Nakagawa)
* Status: Open
* Priority: Normal
* ruby -v: 2.7.0
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
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:

```ruby
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
```



-- 
https://bugs.ruby-lang.org/

[ruby-core:99325] [Ruby master Bug#16854] Using (...) when the method name is a keyword generates error

[nagachika00]

Issue #16854 has been updated by nagachika (Tomoyuki Chikanaga).

Backport changed from 2.5: DONTNEED, 2.6: DONTNEED, 2.7: REQUIRED to 2.5: DONTNEED, 2.6: DONTNEED, 2.7: DONE

ruby_2_7 be359442cb07c25fdc769431ffed3249b9016829 merged revision(s) 71c166e11e761dcaaa943f9b94da38f86ada1bdb.

----------------------------------------
Bug #16854: Using (...) when the method name is a keyword generates error
https://bugs.ruby-lang.org/issues/16854#change-86720

* Author: jamesnakagawa (James Nakagawa)
* Status: Closed
* Priority: Normal
* ruby -v: 2.7.0
* Backport: 2.5: DONTNEED, 2.6: DONTNEED, 2.7: DONE
----------------------------------------
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:

```ruby
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
```



-- 
https://bugs.ruby-lang.org/