Displaying 2 results from an estimated 2 matches for "writablethinstream".
2017 Feb 19
5
RFC: Adding llvm::ThinStream
...en `ThinStream` and existing stream
implementations is that API encourages implementations to be *zero copy*.
Instead of giving it a buffer to write into, it just returns you a slice of
the existing buffer. This makes it *very efficient*. Similar to
`ArrayRef` / `MutableArrayRef`, I also provide *WritableThinStream* for
cases where your data is not read-only. This is another area where
functionality is provided that was not present in existing abstractions
(i.e. writeability).
I have several implementations of this class and some abstractions for
working with them. *ByteStream* and *MutableByteStream* prov...
2017 Feb 22
2
RFC: Adding llvm::ThinStream
...existing stream
> implementations is that API encourages implementations to be *zero copy*.
> Instead of giving it a buffer to write into, it just returns you a slice of
> the existing buffer. This makes it *very efficient*. Similar to
> `ArrayRef` / `MutableArrayRef`, I also provide *WritableThinStream* for
> cases where your data is not read-only. This is another area where
> functionality is provided that was not present in existing abstractions
> (i.e. writeability).
>
> I have several implementations of this class and some abstractions for
> working with them. *ByteStream*...