`Integer#chr` has different `RangeError` exception message compared to CRuby

[postmodern]

I noticed a slight difference between TruffleRuby 22.3.0 and CRuby 3.0.4 while running my test suite against TruffleRuby. When Integer#chr tries to convert an invalid byte (ex: -1) into a character, the RangeError exception message is slightly different on TruffleRuby.

CRuby 3.0.4

-1.chr
# -1 out of char range (RangeError)

TruffleRuby 22.3.0

-1.chr
# -1 is outside of the valid character range (RangeError)

[nirvdrum]

FYI, it looks like you mixed up the attribution. Every version of MRI I tried prints out "-1 out of char range" while TruffleRuby prints out "-1 is outside of the valid character range".

This looks like something we inherited from Rubinius. It's a bit unfortunate because I think the Rubinius message is more helpful. Since MRI has historically changed exception messages at various times, the Ruby Spec Suite specs largely do not check for exact messages, just the exception type and sometimes a message fragment. With that said, we could make this one match MRI, trivially.

[postmodern]

@nirvdrum oops you're right. I still haven't had my coffee yet.

[andrykonchin]

Thank you for report.