Bug #14589: "No implicit conversion of XXX to string" asserion should be handled with an explicit string conversion, and it should be a warning not an assertion

• Status: Rejected
• Assignee: -
• Target version: -
• Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN

Too many people's time have been wasted trying to make sure their puts/prints statements don't assert because of failed implicit string conversions. This should be handled by an explicit .to_s attempt, and a warning instead of a break.

[Hanmac (Hans Mackowiak)]

learn the difference between to_s and to_str
one is explicit, the other is implicit

[nobu (Nobuyoshi Nakada)]

• Is duplicate of Bug #13929: TypeError: no implicit conversion of XXXX into string added

[nobu (Nobuyoshi Nakada)]

• Description updated (diff)
• Status changed from Open to Rejected

It's not a good idea to hide a failure and continue with a garbage.