Bug #1552

String#strip! raises RuntimeError on Frozen String Despite Making No Changes

Added by Run Paint Run Run over 6 years ago. Updated over 4 years ago.

ruby -v:ruby 1.9.2dev (2009-05-28 trunk 23601) [i686-linux] Backport:


Calling String#strip! on a frozen string raises a RuntimeError even if the string was not changed. String#rstrip! doesn't raise an exception in this scenario. I believe that the latter behaviour is correct; #strip! should only raise a RuntimeError if the string would be changed.

$ rubybleed -ve '"ruby".freeze.strip!'
ruby 1.9.2dev (2009-05-28 trunk 23601) [i686-linux]
-e:1:in strip!': can't modify frozen string (RuntimeError)
from -e:1:in

$ rubybleed -ve '"ruby".freeze.rstrip!'
ruby 1.9.2dev (2009-05-28 trunk 23601) [i686-linux]

1.9.1 behaves the same as 1.9.2. 1.8.7 behaves correctly.


#1 Updated by Yukihiro Matsumoto over 6 years ago

  • Status changed from Open to Closed

changed to the opposite way for consistency.

Also available in: Atom PDF