Bug #19087: String#to_c supports multiple "_"

• Status: Closed
• Assignee: -
• Target version: -
• Backport: 2.7: REQUIRED, 3.0: REQUIRED, 3.1: DONTNEED

[andrykonchin (Andrew Konchin)]

I've noticed a minor inconsistent behaviour of String#to_c method. It does not treat a sequence of _ character as an end of meaningful characters:

"123".to_c # => (123+0i)
"12_3".to_c # => (123+0i)
"12__3".to_c # => (123+0i)
"12___3".to_c # => (123+0i)

Similar methods #to_i and #to_r treat multiple _ in a different way - they just ignore characters after it:

"12__3".to_i # => 12
"12__3".to_r # => (12/1)

I would expect #to_c to behave similarly.

---

$ ruby -v
ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-darwin21]

[andrykonchin (Andrew Konchin)]

• Subject changed from String#to_c supports "_" to String#to_c supports multiple "_"

[nobu (Nobuyoshi Nakada)]

• Tracker changed from Misc to Bug
• Backport set to 2.7: REQUIRED, 3.0: REQUIRED, 3.1: REQUIRED

[nobu (Nobuyoshi Nakada)]

https://github.com/ruby/ruby/pull/6645

[andrykonchin (Andrew Konchin)]

Thank you!

[nobu (Nobuyoshi Nakada)]

• Status changed from Open to Closed

Applied in changeset git|c0dc717c45fc3abc64a337c3481bc4555b675d87.

---

[Bug #19087] Disallow successive underscores in Complex string

[nagachika (Tomoyuki Chikanaga)]

• Backport changed from 2.7: REQUIRED, 3.0: REQUIRED, 3.1: REQUIRED to 2.7: REQUIRED, 3.0: REQUIRED, 3.1: DONTNEED

I agree that the new behavior is consistent and preferable, but I don't think it should be fixed on the stable branches.
If there are any troubles on the real world applications with this issue, please let me know.