-
Are there plans to unify blaze-builder with bytestring builder?
-
Constructing a `CI ByteString` will ask for pinned memory, but usually the `ByteString` is short so this behavior not only add overhead but contribute to heap fragment. I think we can do better here, …
-
Example input:
```json
{
"type": "Tx MaryEra",
"description": "Transaction in Mary era.",
"cborHex": "84a5008282582085170c754845947bd9d9310dd9c1bd9a24bab0193bdf4f3f2637bd1e42805a34182182582…
-
We use both lazy and strict version interchangeably everywhere. We need to stick to one. I have a feeling that the lazy version might work everywhere.
See http://blog.ezyang.com/2010/08/strings-in-h…
-
I think it would be good to have the types for strict `Text` and `ByteString` available all the time.
I don't think it's a problem that there is also lazy variants of these, because I feel that if yo…
-
https://hackage.haskell.org/package/bytestring-tree-builder
> According to the benchmarks this builder implementation beats all the alternatives. It is especially well-suited for generating strict …
-
If the content is uses only 7bit encodings and is embedded as ASCII, then getting it as a `String` is easy, but if it's using `Content-Transfer-Encoding: 8bit` then it is necessary to operate on `Byte…
-
I'd propose adding `chunk :: MonadIO m => ChunkSize -> ConduitT ByteString ByteString m ()` to conduit as it seems quite common use case to chunk up a bytestring stream (for example when uploading to …
-
Have you considered using `ByteString` internally, rather than `Text`? Considering bech32 values are likely to be stored/serialized as plain `ByteString`s, seeing as they don't need any special encodi…
-
I'm surprised there exists no encoder for that: https://hackage.haskell.org/package/waargonaut-0.8.0.1/docs/Waargonaut-Encode.html#g:4