[ruby/net-protocol] Undo BufferedIO#rbuf_consume_all_shareable! optimization

This optimization is unsafe because `dest` is allowed to be a custom
object responding to `<<` (e.g. a block wrapped in `ReadAdapter`).

So the receiver can hold onto the passed buffer for as long as it wants.

If it was guaranteed that `ReadAdapter` was the only possible receiver
we could dup the buffer there for mutation safety, but I'm not certain
it's the case so I'd rather err on the safe side.

Ref: https://github.com/shrinerb/shrine/issues/610

https://github.com/ruby/net-protocol/commit/7efa16d55d

0 files changed, 0 insertions, 0 deletions