From: nobu@...
Date: 2016-02-19T02:20:47+00:00
Subject: [ruby-core:73884] [Ruby trunk Feature#12043] Add a method to NoMethodError that tells if private methods are callable at the time of

Issue #12043 has been updated by Nobuyoshi Nakada.


This feature is **only** for "did_you_mean" gem, so I think that any name is OK, including implementation details.

`private_call?`
`explicit_receiver?`
`fcall?`
`were_you_a_function?`
`demon_from_the_nose?`
etc.

----------------------------------------
Feature #12043: Add a method to NoMethodError that tells if private methods are callable at the time of 
https://bugs.ruby-lang.org/issues/12043#change-57049

* Author: Yuki Nishijima
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
I've briefly talked about this to Sasada-san, but also wanted to hear from other committers. I would like to add a method to `NoMethodError` that tells whether or not private methods are callable from the line where the exception is raised. An example would be like this:

```ruby
begin
  raies "Error" # 
rescue NoMethodError => no_method_error
  no_method_error.private_method_callable? # => true
end
```

The only use case I can think of is [the spell checker in the did_you_mean gem](https://github.com/yuki24/did_you_mean/blob/c4f0247/lib/did_you_mean/spell_checkers/method_name_checker.rb#L18) and I'm not actually sure how useful it would be for others.

Please let me know what you think, I'm open to suggestions.



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

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>