Why doesn't Ruby have a real StringBuffer or StringIO?

James A. Rosen picture James A. Rosen · Aug 13, 2008 · Viewed 27.3k times · Source

I recently read a nice post on using StringIO in Ruby. What the author doesn't mention, though, is that StringIO is just an "I." There's no "O." You can't do this, for example:

s = StringIO.new
s << 'foo'
s << 'bar'
s.to_s
# => should be "foo\nbar"
# => really is ''`

Ruby really needs a StringBuffer just like the one Java has. StringBuffers serve two important purposes. First, they let you test the output half of what Ruby's StringIO does. Second, they are useful for building up long strings from small parts -- something that Joel reminds us over and over again is otherwise very very slow.

Is there a good replacement?

It's true that Strings in Ruby are mutable, but that doesn't mean we should always rely on that functionality. If stuff is large, the performance and memory requirements of this, for example, is really bad.

result = stuff.map(&:to_s).join(' ')

The "correct" way to do this in Java is:

result = StringBuffer.new("")
for(String s : stuff) {
  result.append(s);
}

Though my Java is a bit rusty.

Answer

Mike Stone picture Mike Stone · Aug 13, 2008

I looked at the ruby documentation for StringIO, and it looks like what you want is StringIO#string, not StringIO#to_s

Thus, change your code to:

s = StringIO.new
s << 'foo'
s << 'bar'
s.string