From: funny.falcon@... Date: 2018-07-13T04:52:22+00:00 Subject: [ruby-core:87934] [Ruby trunk Bug#14909] Method call with object that has to_hash method crashes (method with splat and keyword arguments) Issue #14909 has been updated by funny_falcon (Yura Sokolov). Why your object has `to_hash` method? Ruby uses long named methods for implicit conversion: `to_str` - if your object should act as a string, `to_int` - if your object should act as an integer, `to_ary` - if your object should act as an array. Looks like same for `to_hash`. For explicit conversion short names are used: `to_s`, `to_i`, `to_a`, `to_h`. ---------------------------------------- Bug #14909: Method call with object that has to_hash method crashes (method with splat and keyword arguments) https://bugs.ruby-lang.org/issues/14909#change-72941 * Author: johannes_luedke (Johannes L��dke) * Status: Feedback * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin17] * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN ---------------------------------------- In a method with a splat method argument followed by a keyword argument, it leads to an `ArgumentError` when calling the method with an object that reacts to `to_hash` ~~~ruby def my_func(*objects, error_code: 400) objects.inspect end class Test def to_hash # an example hash { to_hash_key: "to_hash" } end end my_func(Test.new) ~~~ Observed result: an exception is raised: `in my_func: unknown keyword: to_hash_key (ArgumentError)` Expected result: `[#]` is returned by the `my_func` call It should behave the same when calling with objects that have a `to_hash` method and objects that don't, shouldn't it? -- https://bugs.ruby-lang.org/ Unsubscribe: