ruby.git/test/ruby/test_nomethod_error.rb, branch v4.0.2

Fix bad NameError raised using sendforward instruction through vcall

2025-08-27T18:14:29+00:00

If you called a VCALL method and the method takes forwarding arguments
and then you forward those arguments along using the sendforward instruction,
the method_missing class was wrongly chosen as NameError instead of NoMethodError.
This is because the VM looked at the CallInfo of the vcall and determined it needed
to raise NameError. Now we detect that case and raise NoMethodError.

Fixes [Bug #21535]

Do not include a backtick in error messages and backtraces

2024-02-15T09:42:31+00:00

[Feature #16495]

Update some tests for the new message format of NoMethodError

2023-02-20T01:33:06+00:00

[WIP] add error_squiggle gem

2021-06-29T14:45:49+00:00

```
$ ./local/bin/ruby -e '1.time {}'
-e:1:in `': undefined method `time' for 1:Integer (NoMethodError)

1.time {}
 ^^^^^
Did you mean?  times
```

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

Fix segmentation fault when `Module#name` returns non string value [Bug #17754]

2021-03-27T23:47:42+00:00

* Add test for NoMethodError#to_s does not segfault

* Ensure no segfault even if Module#name is overridden

Make test for no method error more reliable

2020-06-06T17:48:24+00:00

This test should not depend on the bahaviour of the did_you_mean gem.

Split test_nomethod_error.rb

2019-12-31T10:43:36+00:00