From: "fuadksd (Fuad Saud)" Date: 2013-10-16T12:12:07+09:00 Subject: [ruby-core:57898] [ruby-trunk - Feature #9025] Clarify the error message when calling a method with the wrong number of arguments Issue #9025 has been updated by fuadksd (Fuad Saud). Maybe. Sometimes, if you do chain a couple of methods, you may get confused. I'm not saying there's no way you can figure out what's happening in the current situation, I just feel like the method name belongs here, as it belongs in NoMethodError messages. ---------------------------------------- Feature #9025: Clarify the error message when calling a method with the wrong number of arguments https://bugs.ruby-lang.org/issues/9025#change-42493 Author: Nerian (Gonzalo Rodr��guez) Status: Open Priority: Normal Assignee: Category: Target version: Currently when calling a method with the wrong number of arguments we get a confusing error message: ArgumentError: wrong number of arguments (1 for 0) That means that the method was meant to accept 0 arguments, but 1 was provided instead. This error message is confusing, and a large number of people had to search for its meaning. For example [1] has 11000 views. I propose that we change the error message to something whose meaning is obvious. Examples: * ArgumentError: wrong number of arguments (expected: 1, provided: 0) * ArgumentError: wrong number of arguments (1 instead of 0) This ticket originated from this pull request: https://github.com/ruby/ruby/pull/367 [1] http://stackoverflow.com/questions/7537450/what-does-wrong-number-of-arguments-1-for-0-mean-in-ruby -- http://bugs.ruby-lang.org/