Issue #19978 has been updated by sawa (Tsuyoshi Sawada). Do you intend the elided inspect form to be defined for each class, or should it be a result of simple string ellipsis on a fully expanded inspect string (e.g., take the first ten and last seventeen characters from inspection, as in your example)? If you intend the former, the implementation is not going to be trivial. ---------------------------------------- Feature #19978: NoMethodError and large objects should not create unwieldy error messages https://bugs.ruby-lang.org/issues/19978#change-105103 * Author: ConorOBR (Conor O'Brien) * Status: Open * Priority: Normal ---------------------------------------- # Description Currently, in the error message for `NoMethodError`, the object in question is inspected and displayed to the user. This results in unwieldy error messages for large objects. This comes up most often for me when working with large hashes, but in principal it affects any object with an `inspect` method which can produce large output. # Reproduce There are many ways to reproduce this, but here is one. (Scales with the size of the object, so this gets out of hand quickly with, say, `1e7` as the upperbound.) ```rb (1..1e3).to_a/=3 ``` # `ruby -v` ``` ruby 3.2.2 (2023-03-30 revision e51014f9c0) [x64-mingw-ucrt] ``` # Desired Behavior Some kind of elision, e.g., for the above, the desired output could be something like ```rb -e:1:in `<main>': undefined method `/' for [1, 2, 3, ..., 998, 999, 1000]:Array (NoMethodError) (1..1e3).to_a/=3 ^ ``` At the very least, not showing the entire object (even if that means showing none of it) if the `inspect` exceeds a certain length would be preferable. -- https://bugs.ruby-lang.org/

Issue #19978 has been updated by mame (Yusuke Endoh). Status changed from Open to Closed The behavior will be changed at Ruby 3.3. See #18285. ---------------------------------------- Feature #19978: NoMethodError and large objects should not create unwieldy error messages https://bugs.ruby-lang.org/issues/19978#change-105107 * Author: ConorOBR (Conor O'Brien) * Status: Closed * Priority: Normal ---------------------------------------- # Description Currently, in the error message for `NoMethodError`, the object in question is inspected and displayed to the user. This results in unwieldy error messages for large objects. This comes up most often for me when working with large hashes, but in principal it affects any object with an `inspect` method which can produce large output. # Reproduce There are many ways to reproduce this, but here is one. (Scales with the size of the object, so this gets out of hand quickly with, say, `1e7` as the upperbound.) ```rb (1..1e3).to_a/=3 ``` # `ruby -v` ``` ruby 3.2.2 (2023-03-30 revision e51014f9c0) [x64-mingw-ucrt] ``` # Desired Behavior Some kind of elision, e.g., for the above, the desired output could be something like ```rb -e:1:in `<main>': undefined method `/' for [1, 2, 3, ..., 998, 999, 1000]:Array (NoMethodError) (1..1e3).to_a/=3 ^ ``` At the very least, not showing the entire object (even if that means showing none of it) if the `inspect` exceeds a certain length would be preferable. -- https://bugs.ruby-lang.org/