This is cool, thanks Zach!
Another set of mostly-isomporphic types that this could be applied to is
different matrix/array types in core.matrix. core.matrix already has
generic conversion mechanisms but they probably aren't as efficient as they
could be. I'll take a look and see if the same
I have already used this library and it is really really useful. Thanks
Zach.
Thomas
--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated -
Ropes?
http://en.m.wikipedia.org/wiki/Rope_(data_structure)
Ben
--
This message was sent via electromagnetism.
On 02.07.2013, at 12:19, Mikera mike.r.anderson...@gmail.com wrote:
This is cool, thanks Zach!
Another set of mostly-isomporphic types that this could be applied to is
different
Hey Mike,
Please feel free to appropriate or adapt any code you think might be
useful. I've signed a CA, it should all be kosher.
As far as an immutable byte-data type, I'm a little skeptical it would be
useful in a wide variety of situations, since a dense array/matrix is going
to be much
The library defines two protocols, ByteSource and ByteSink. They expose a
'take-bytes!' and 'send-bytes!' method, respectively. An unoptimized
transfer involves shuttling bytes between these two methods, which in most
cases means one copy and one allocation (ByteBuffer can act as a ByteSource
Very cool, I've got a couple of question: the readme references optimized
transfers, what qualifies as an optimized transfer? Also, would it be
possible for byte-streams to give an estimation of the number of memory
copies that happen in a given conversion (maybe this is as simple as the
I've recently been trying to pull out useful pieces from some of my more
monolithic libraries. The most recent result is 'byte-streams' [1], a
library that figures how how to convert between different byte
representations (including character streams), and how to efficiently
transfer bytes
