Calling unsafe methods which don't return a string shouldn't fail

[dmathieu]

Unsafe methods are always calling #to_str when called so the object returned is a new string object.

If the original method doesn't return a string, like gsub with only one argument though, it'll fail as there's no to_str method.

[dmathieu]

I have just changed my commit, to simplify the logic of the improvement.

[fxn]

send accepts strings, no need to create a symbol from them.

[dmathieu]

Actually, as we're in a class_eval and the method name is a variable, I must either create a string or a symbol.
For micro-performances reasons, symbols are then better as it wouldn't create a new object instance if the same symbol has already been called.

[dmathieu]

@fxn : what I mean is, anyway, we must either create a string or a symbol.
Creating a symbol avoids creating a new object every time the method is called.

[fxn]

Would it be better to interpolate unsafe_method as an ordinary method call?

[dmathieu]

Oh ok, right, I definitely can do that.

[dmathieu]

I have updated my commit.

[fxn]

Excellent, thank you :).