You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gary D. Gregory (Jira)" <ji...@apache.org> on 2021/09/26 14:23:00 UTC
[jira] [Closed] (IO-732) Char equivalent of
UnsynchronizedByteArrayOutputStream (and InputStream)
[ https://issues.apache.org/jira/browse/IO-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary D. Gregory closed IO-732.
------------------------------
Resolution: Won't Do
PR closed per [jochenw|https://github.com/jochenw]'s comment.
> Char equivalent of UnsynchronizedByteArrayOutputStream (and InputStream)
> ------------------------------------------------------------------------
>
> Key: IO-732
> URL: https://issues.apache.org/jira/browse/IO-732
> Project: Commons IO
> Issue Type: New Feature
> Components: Streams/Writers
> Affects Versions: 2.8.0
> Reporter: PJ Fanning
> Priority: Major
> Time Spent: 2h
> Remaining Estimate: 0h
>
> I was thinking of writing this and submitting it but just want to see if people think it makes sense first.
> The idea is to take AbstractByteArrayOutputStream and to replace the byte[] with char[] (maybe called AbstractCharArrayWriter) and to create an UnsynchronizedCharArrayWriter that extends it. Could so something similar with UnsynchronizedByteArrayInputStream - to get an UnsynchronizedStringReader.
> The nice thing about AbstractByteArrayOutputStream is the way it avoids arraycopy. The existing commons-io StringBuilderWriter still has arraycopy under the hood (in the java.lang.StringBuilder).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)