Documentation about fast_try HOT 5 OPEN

Sorry I guess I need to change the description of that limitation. It appears to break only when the method does not exist on the class. For example:

Array&.bad_method 
#=> NoMethodError: undefined method `bad_method' for Array:Class

Class&.to_s&.class&.bad_method
#=> NoMethodError: undefined method `bad_method' for String:Class

Let me know if you know how to get around this without killing any performance

from fast_try.

There is nothing you can do without impacting performance of the safe operator because all additions would require method calls. I think the simplest solution if you really intended to make it more similar to ActiveSupport#try would be:

self&.public_send(a,*b,&c) if respond_to?(a) 

This nearly identical to how ActiveSupport handles it in try

from fast_try.

Yeah that was the only other solution I had determined. However then it will no longer behave like safe navigation (and I dont think it needs the safe navigation anymore either).

from fast_try.

the safe navigation only offers assistance to nil so it would work in the identical fashion it currently does excepting the fact that it will return nil if the object does not respond to the method name rather than raising a NoMethodError.

e.g.

def simple_test(obj,method_name)
    if obj.respond_to?(method_name)
       puts "#{obj.inspect} responds to #{method_name}"
       obj&.public_send(method_name) 
   end
end


simple_test(nil,:to_s) 
# nil responds to to_s
#=> nil 
simple_test("a",:to_s)
# a responds to to_s
#=> "a"
simple_test(
     simple_test("a",:non_existent) # this will return nil
,:to_s)
# nil responds to to_s
#=> nil 

Safe navigation is not meant to be a replacement for try but rather it is meant to make it "safe" to call methods when you are expecting an object that you expect to respond to the method call or nil. eg

h = {r: 12}
h[:r]&.to_i
#=> 12
h[:p]&.to_i
#=> nil

Here I know that Hash#[] will return an object (which I expect to respond to to_i) or it will return nil if the key does not exist

from fast_try.

Hmm interesting, however to_s is a bad use case for this method but its a limitation none-the-less.

Given all the differences it seems I may change the name of this repo to something else.

from fast_try.