4 ms·
What's with the "dude" and "totally radical"? The problem with [Char] for bulk text IO was well acknowledged when I wrote bytestring. To quote: "The Haskell S
by dons 14y ago
What's with the "dude" and "totally radical"?
The problem with [Char] for bulk text IO was well acknowledged when I wrote bytestring. To quote:
"The Haskell String type is notoriously inefficient. We introduce a new data type, ByteString, based on lazy lists of byte arrays, combining the speed benefits of strict arrays with lazy evaluation. Equational transformations based on term rewriting are used to deforest intermediate ByteStrings automatically. We describe novel fusion combinators with improved expressivity and performance over previous functional array fusion strategies. A library for ByteStrings is implemented, providing a purely functional interface, and approaches the speed of low-level mutable arrays in C."
- unoti 14y agoThat sounds cool, and a lot like Erlang's iolists, right? The idea being that lists of byte arrays lets you do IO without all the memcpy that might otherwise be required?